On Mon, Nov 05, 2007 at 01:16:13AM -0600, Aaron Griffin wrote:
On 11/4/07, Jason Chu <jason@archlinux.org> wrote:
On Sun, Nov 04, 2007 at 05:55:07PM -0600, Dan McGee wrote:
On Nov 4, 2007 5:20 PM, Jason Chu <jason@archlinux.org> wrote:
If I use the mkarchroot and makechrootpkg scripts to build packages, I need to have sudo installed. Using the current mkarchroot options I have to specify "base base-devel sudo". I just need to know if we're planning on putting sudo into base-devel or if I should update the mkarchroot and makechrootpkg scripts to reflect this.
I put it into base/support, just like ssh and other tools that aren't "essential" but also aren't development tools. So no, I think its going to stay right there.
Should we create a base-support group so that mkarchroot can create a chroot with 'mkarchroot chroot base base-devel base-support'?
How's that any different though? Seems like you're actually going to get MORE than you need (ssh and the like).
I know it's not pretty, but I couldn't figure out a better way to handle sudo. And I don't want to restructure the repos strictly for the sake of one tool
It was just a suggestion. It was the best I could come up with that didn't involve installing sudo explicitly. Jason