Danek Duvall wrote:
Liane Praza wrote:
I think the current convention is to put this under 122/common, but
correct me if I'm wrong.
I think that's the sanest thing to do. Ultimately, what I think we'd want
is a package whose release version has the build id in it, and whose
dependencies are generally unconstrained, except when there's a minimum
version required. Thus "os...@122" (or something) is the thing you want to
install if you want to build build 122 of ON. But our current publication
methods make this harder to do than is probably worth it right now. Your
current plan is probably the sanest next best thing.
Yeah, I'm planning on trying something more like you describe in my ON
repo, since it isn't tied to the import.py style of publication. But for
the main release right now, I think this is sufficient.
(I expect that since I was already made a leader and have done my 3
commits that it's OK for me to commit directly after review is
complete. Please let me know if not.)
Yup.
OK, thanks. If I don't hear any negative comments by Monday afternoon,
I'll push.
liane
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
