Dan Price wrote:
On Fri 01 May 2009 at 07:03PM, Bart Smaalders wrote:
http://cr.opensolaris.org/~barts/8604/
http://defect.opensolaris.org/bz/show_bug.cgi?id=8604
(yes, I'll fix the copyright date :-)).
Slurps up the catalog from a repo; find the specified pkgs
(recursively if requested) and prints a list of files to
copy from one repo hierarchy to another to move those pkgs.
Apparently, build 111 requires 264244 files for manifests
and data. Yow.
Bart and I discussed this offline, but I want to mention for discussion
is how doing this will impact the update log. I am concerned that
we will have to blow away the catalog to make this work. Is that
an unfounded concern?
No, it isn't unfounded. Without entries added to the updatelog, the
only way to get the server to see these new packages is to run the depot
with --rebuild and that would blow away the existing updatelog which
would also nuke incremental updates for all users that had an older
version of the catalog.
It should be sufficient to open the updatelog and call add_package() on
it just as we do in modules/server/transaction.py:accept_publish.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
