On Thu, 23 Oct 2008 00:16:03 +0200
"Martin Bochnig" <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 22, 2008 at 11:40 PM, Martin Bochnig <[EMAIL PROTECTED]> wrote:
> > On Wed, Oct 22, 2008 at 11:28 PM, Shawn Walker <[EMAIL PROTECTED]> wrote:
> >
> >> I would venture to guess that a significant majority of users will never
> >> need to or want to recompile or alter the software as you suggest.
> >>
> >> They're going to want a stable, tested version of the software, and that
> >> means a pre-built, pre-configured binary that's been signed by their
> >> vendor.
> >>
> >> Since you need or want a more flexible system, I'd suggest you discuss
> >> it with the pkgbuild folks.
> >
> >
> > Or on conary, which features "cooking source recipes".
> > It is as easy as this:
> >
> > # conary emerge --no-deps bash:source=3.2.10-7
> >
> > (build bash and makes a binary set of "troves" out of it, which then
> > constitute a binary package that is under conary's control in its
> > database backend.
> >
> > Configuring the "recipes" can be comapred to setting up spec files for
> > pkgbuild (or rpmbuild).
> >
>
> Without "--no-deps" it would look like this:
>
> # LD_PRELOAD=/tmp/y/a.out conary emerge bash:source=3.2.10-7
> + Methods called:
> Bash.setup
> + Building [EMAIL PROTECTED]:devel[~!bootstrap,~buildtests]
> error: Could not find the following troves needed to cook this recipe:
So what do I have to tell it to get it to build and/or install all
the things it didn't find? That's what makes a package manager a real
winner - that it will quietly go out and install all the dependencies
needed for the package you asked for.
Likewise, that's what makes a good ports system a real win - that it
will go out and install - or build if necessary, or even build but not
install if sufficient - the dependencies needed for the package I
asked for.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
_______________________________________________
opensolaris-discuss mailing list
[email protected]