<div class="gmail_quote">On Mon, Aug 24, 2009 at 12:27 AM, Maciej (Matchek) Blizinski <span dir="ltr"><<a href="mailto:maciej@opencsw.org">maciej@opencsw.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
</div>+1<br>
<br>
pyantlrrt --> py_antlrrt<br>
pyyaml --> py_yaml<br>
<br>
How do we go about the change? Modify catalogname without touching<br>
pkgname? Will the usual pkg-get/pkgutil update do the right thing?<br>
<font color="#888888"></font></blockquote><div><br>dependancies are based on CSWname, not software name, so it should "do the right thing". The places where it will break, are where admins may have saved procedures, that do things like:<br>
<br>machine1$ pkg-get -l >save-list<br> #time passes...<br>machine2$ pkg-get -i `cat save-list`<br><br><br></div></div><br>Not to mention, changing softwarename is kinda a pain for me to deal with. But if there are "only a few", then all right.<br>
<br>WITH THE EXCEPTION that, as someone noted, things with actual recognized name of "pyfoo", should REMAIN "pyfoo", not be artificially split to be "py_foo" in that case.<br><br><br>