* Shawn Walker <[email protected]> [2010-05-18 18:19]: > On 05/18/10 06:00 PM, Stephen Hahn wrote: > >* Shawn Walker<[email protected]> [2010-05-18 15:43]: > >>On 05/18/10 04:57 PM, Stephen Hahn wrote: > >>> 4. (5.4) Using a .p5p archive as an origin is... unusual. I would > >>> have expected the .p5p to deliver the origin(s) in the included > >>> .p5i files, the content of any packages within the .p5p, and then > >>> be safely discarded. The current writeup suggests I have to > >>> carefully manage my .p5p files, which seems dangerous. Could we > >>> get the publisher/.p5p lifecycle envisioned in the document stated > >>> more clearly? > >> > >>I don't quite understand the concern about having to carefully > >>manage .p5p files. > >> > >>My assumption here was that .p5p files enable the complete offline > >>delivery of package data and could be aggregated with any already > >>existing package data for related publisher(s). > >> > >>The intent is that the client works identically to what it does > >>today, and that .p5p files are simply treated as additional package > >>data sources that exist only for the duration of a transaction. > >> > >>Could you expound a bit on your possible concerns here and/or what > >>you mean by "deliver the origin(s)"? > > > > "Deliver the origin(s)" means that the origin of each publisher in the > > .p5p is provided in the corresponding .p5i. > > > > I am thinking about how "pkg fix" is expected to work for content > > initially delivered by .p5p. I know we have disconnected sites as a > > key use case, so archiving the .p5p locally is one way to make pkg fix > > work. > > A simple compromise for the moment would be to simply cache any > package data requested from a .p5p archive in the client's download > cache for now. That would at least make the .p5p case no worse off > than the pkg fix for offline or no longer available publisher case. > I could also add -g support for pkg fix.
.p5p -> download cache for fix: +1 pkg fix -g: 0 (low priority) Thanks for the other parts of the response as well. - Stephen _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
