<div class="gmail_quote">On Thu, Mar 12, 2009 at 5:00 PM, Phillip Warner <span dir="ltr"><<a href="mailto:phillip.c.warner@gmail.com">phillip.c.warner@gmail.com</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;">
Mauro,<br>
<br>
the latest attached patch looks fine, but I don't have time to<br>
thoroughly test it right now.</blockquote><div><br>No problem. I'll wait a little more for a review (from anybody). After that, I can always apply it and wait for the bug reports :-)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Another issue that might come up with this renames business is<br>
orphaned .sbopkg files. �When a SlackBuild is renamed the old one is<br>
removed from the repo, but if you have any .sbopkg files in there they<br>
are not migrated over to the new SlackBuild folder. �Perhaps after the<br>
rsync a quick scan can be run to determine if there are any folders<br>
with .sbopkg files that don't have corresponding .SlackBuild files.<br>
If such a folder is found you could be given the option to have those<br>
.sbopkg files moved to the renamed folder (and have the old folder<br>
removed). �The user could then modify the .sbopkg files as needed.</blockquote><div><br>Eh, not as easy/quick as it looks.<br>�</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A similar .sbopkg migration might be desired once a new repo<br>
(Slackware 13) is in place.</blockquote><div><br>I get your points, but I don't think these are realistic features for 0.27.x or 0.30.0. Your best bet is to open two Enhancement tickets on the issue tracker, so that your suggestions don't get lost.<br>
</div></div><br>-- <br>Mauro Giachero<br>