On Thu, Jul 15, 2010 at 03:13:09PM -0400, Kyle McDonald wrote: > While Dev builds probably won't ever have Repository ISO's (and I don't > need one as I can't imagine needing to burn one.) I'd like to continue > keeping a mirror of a sliding window of the 5 latest builds, and every > 5th build before it. > > Basically as time passes I want to be able to thin out the 'past' in the > repository. I'm just not sure what tools/features are available, and how > to use to them to manage this in the best way.
My suggestion would be to put each dev build in its own repository. Although the client doesn't support it yet, Shawn is working on the ability for client to compose multiple disjoint repositories for a single publisher into one unified view. In this model, you'd be able to add just the repos you're interested in to the client, and it would download the packages from there. Also, if you have each build in its own repo, you can merge these into another repo until the client supports this composition. > One option is to mirror each build separately on ZFS with Dedup. > If it were possible to prune whole builds from the repository at a later > date, then I could mirror the whole thing and remove what I don't need. > The trick there would be keeping it from re-appearing - at least with rsync. I think we'll eventually support the ability to remove packages from a repository, but we don't currently have this feature today. We're considering removing rsync support in favor of enhancing pkgrecv(1) to examine a source repository and pull down missing packages from a destination repository. This is mostly because rsync is slow, and is detrimental to the filesystem performance on our servers. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
