* Chris Quenelle <[EMAIL PROTECTED]> [2008-02-02 03:15]: > Stephen Hahn wrote: > > Agreed, but I want to delay the development of this capability, since > > the operations will necessarily be a subset of the server-based > > operations (and also because I do want the various projects, community > > groups, and other upstream sources delivering via the active APIs and > > not via file-packages--that is, I want to change and expose the > > publication processes as well). > > Is there more documentation for how you expect to "change and expose > the publication process" ? Not yet. We're making notes based on how the assembly of the preview releases has been going.
> It doesn't seem possible to internally manage the creation and delivery > of these packages without an on-disk format. If you have other ideas, > I'd be interested to read more about them. I obviously can't see "impossibility"--if repository-repository relationships are well-defined, then an independent, on-disk representation is not needed during the development and release processes. For instance, the current "deliver SysV packages to RE dock" is equivalent to "send pkg(5) package contents to RE repository". The current "build SysV packages" becomes "send pkg(5) package contents to test or temporary repository". Etc. The independent on-disk format is primarily for (a) software vendors that are unable to run a repository and (b) sites that don't wish to, or have software installation policies that require more control than the repository model offers. It shouldn't be needed in a development process where repository operation is permitted. - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
