Dennis Clarke wrote:
also .. what is the purpose of this ?

I'd find these recipes very useful.  Often, a binary package comes
close, but doesn't entirely fit the needs of an organization.
By using these recipes, I'd  able to more easily build packages that fit
my needs.

well we can currently do pkg-get -i foo for some package named foo. This
does a fine job of fetching all the dependencies that you can shake a stick
at.

Exactly. Sometimes, Blastwaves' packages have more dependencies than I care to shake a stick at. Here's the problem: Blastwave maintainers tailor the package dependencies to *their* requirements. Not mine. This not meant to disparage their work, as I frequently make use of Blastwave's packages, and find them to be of excellent quality; but sometimes, there are dependencies that don't fit into what I wish to accomplish.


The ultimate would be pkg-get -b foo where all the sources for foo along
with all dependency sources would be fetched into /opt/csw/src and then
built with the Studio 11 compiler that must be installed.

would be a murderously long process but some people seem to want that.

No, I believe that I and others would like to leverage what the package maintainers have accomplished. By using their recipes as starting point to build packages, we can tailor those packages to our requirements.

This is something that the Debian project can do with aptitude these days.
Pretty cool if you ask me.

Yep, the *BSD ports system does pretty much the same thing. However, the package maintainer's wishes regarding what constitutes a dependency rule.



I have all the sources here jammed into the NFS server and multiple revs of
most things. The GAR system has a lot in it but not everything. It just
feels like a never ending pile of work to keep pushing forwards sometimes.

Really .. I'd *love* to fetch sources and build on the fly also but
implementing the infrastructure and testing the process will take a LOT of
work and time.


No rest for the wicked ;)

Why not let those who are adventurous enough, build packages to fit their needs by using (and modifying) the recipes of those who've gone before?


John
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to