[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread Jack Doerner
Returning a few messages back to the issue with calling sudo: it would seem to me that the solution is to check to see if sudo is installed. If it's installed, ask if you want to install the builddeps, and if it's not, just list the builddeps as it already does. The majority of users will have sud

[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread Michael K. Johnson
On Wed, Jun 03, 2009 at 05:59:43PM +0200, Martin Baehr wrote: > On Wed, Jun 03, 2009 at 11:34:34AM -0400, Michael K. Johnson wrote: > > > another goal that is often requested is to be able to install all needed > > > compilation tools for local (non conary) use. > > That should be a group or simpl

[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread Martin Baehr
On Wed, Jun 03, 2009 at 11:34:34AM -0400, Michael K. Johnson wrote: > > another goal that is often requested is to be able to install all needed > > compilation tools for local (non conary) use. > That should be a group or simple list of packages. Making a recipe > do that is kind of making use o

[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread Michael K. Johnson
On Wed, Jun 03, 2009 at 03:56:54PM +0200, Martin Baehr wrote: > On Wed, Jun 03, 2009 at 09:30:18AM -0400, Michael K. Johnson wrote: > > First, I want to keep the sights on the end goal, which I conceive > > to be, fundamentally, quick builds for doing dependency discovery > > and for local installs

[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread Martin Baehr
On Wed, Jun 03, 2009 at 09:30:18AM -0400, Michael K. Johnson wrote: > First, I want to keep the sights on the end goal, which I conceive > to be, fundamentally, quick builds for doing dependency discovery > and for local installs for initial testing. another goal that is often requested is to be a

[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread Michael K. Johnson
First, I want to keep the sights on the end goal, which I conceive to be, fundamentally, quick builds for doing dependency discovery and for local installs for initial testing. The end goal is to be able to use rMake for this as well -- to have a "dependency discovery chroot" that has *everything*

[Foresight-devel] Re: conary and build requirement

2009-06-03 Thread ermo | Rune Morling
I've been thinking about this as well. To put it in the proper context (no pun intended) aren't we presently exploring a Foresight use case and the associated developer workflow that is possibly general enough to be of benefit outside of Foresight? From my perspective, we're looking at the situatio