> Yeah, local replication is maybe that what comes close. So I have done > this with a combination of pkgrecv + pkgsend.
I'm impressed that works at all, actually. pkgrecv was intended as a way of capturing content for publication elsewhere, not as a replication mechanism. > So I get identical packages but in different authorities. It's not an > issue today, but if someone wants to upgrade the local provided > packages with newer packages coming from opensolaris.org, he would > never see that there is an update for his installed package :-( I once the namespace issues are resolved, authority won't matter unless it's part of the package name. In that case, the upgrade between authorities should work seamlessly. I believe you can get around this problem today by changing your preferred authority back to opensolaris.org and upgrading. If you're asking that your local depot stay in sync with opensolaris.org, we're not to the point of having that functionality. We're looking at mirroring content, but I'm not sure if we want to mirror meta-data. I'll let Stephen comment more on that, if he so desires. As far as having operations be fast on the client, we'd eventually like to write a client-side cache. We have the beginnings of that today. The client in the gate will keep ahold of content to speed up download, and to recover should a download fail. Eventually, we'd like to have something fancies that hangs around, retrieves files in parallel on behalf of the pkg client, and perhaps shares this content if appropriate. This would be akin to having your depot run locally, but wouldn't provide so many administration headaches (I hope). That's still a way out, though. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
