On Thu, Dec 11, 2008 at 12:34:44PM -0600, Nicolas Williams wrote: > On Thu, Dec 11, 2008 at 12:33:23PM -0600, Shawn Walker wrote: > > I'm pretty sure we are saying the same thing then: > > > > set info.spec_url = http://spec-files/foo.spec > > set info.source_url = http://source-files/foo.tar.gz > > > > Right? > > Yes. That's what I want. And that's what I was pretty sure was the > plan.
Let me argue with myself for a minute though and bring up a point that I could swear I made some months ago. Suppose we could: a) include everything you need to re-build from source as a facet and, crucially, b) that we could have facets that are not even downloaded by default. Add in c) suppose that we could represent build dependencies much the same way as pkg dependencies (they are, after all, very similar). Then we could dispense with an SCM repository for the spec file and tarballs without costing users nor mirrors anything, and we could eliminate duplicate code (for dealing with build dependencies). Now, I won't argue that we should wait for that (b) and (c), so (a) is out of the question for now. But it'd sure be nice if we could do this. Also, regarding 1-tarball-to-many-pkgs, the above would cover that: one pkg has the sources, the others have a build dependency on that one pkg. A related point: for security purposes we're going to want to include cryptographic hashes of everything referenced by URL that is needed to rebuild a pkg. Nico -- _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
