Tim Foster wrote: > On Tue, 2010-06-15 at 14:42 -0700, [email protected] wrote: >>> I'll have a look - I assumed people were only ever importing into >>> repositories that looked like the production ones. It sounds like the >>> right thing to do would be to query the repository for the publisher >>> prefix it provides, and use that instead. >> I ran across this as well when doing the build 142 resync as I >> typically use a different publisher than "opensolaris.org" as part of >> the import. > > Alright, I'll file a bug and start working on the fix right away. > >>> Feel like starting to write some unit tests for importer.py - or better >>> yet, start transitioning over to using the real publishing tools? >> To be fair, the importer is still the primary way packages get into >> RE's repo. :-) > > Do we have a time line to get consolidations to move?
+1 As soon as the WOS RE team is ready to receive IPS packages from unbundled teams, I would be glad to start delivering them instead of the hokey way we deliver SYSV package today. This would simplify my life considerably. But I understand that there are priorities and resource constraints involved. You might want to make WOS Consolidations a higher priority than unbundleds. Or vice versa, I don't really know. Tier 1 is ON. Tier 2 is Other WOS consolidations. Tier 3 is people who grab a hold on the caboose as it hurtles by (unbundled). --chris > In this case at > least, writing the extra code to teach importer.py about SMF > dependencies was a bit time consuming and (in this case, obviously) > prone to error (sorry again) > > cheers, > tim > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
