[sbopkg-users] renames bugs - sbopkg 0.27.0

Phillip Warner phillip.c.warner at gmail.com
Thu Mar 12 16:00:28 UTC 2009


Mauro,

the latest attached patch looks fine, but I don't have time to
thoroughly test it right now.

Another issue that might come up with this renames business is
orphaned .sbopkg files.  When a SlackBuild is renamed the old one is
removed from the repo, but if you have any .sbopkg files in there they
are not migrated over to the new SlackBuild folder.  Perhaps after the
rsync a quick scan can be run to determine if there are any folders
with .sbopkg files that don't have corresponding .SlackBuild files.
If such a folder is found you could be given the option to have those
.sbopkg files moved to the renamed folder (and have the old folder
removed).  The user could then modify the .sbopkg files as needed.

A similar .sbopkg migration might be desired once a new repo
(Slackware 13) is in place.

--phillip

On 3/11/09, Mauro Giachero <mauro.giachero at gmail.com> wrote:
> The attached patch (on top of r498) fixes the problem here.
> Unless any problems arises, I'd like to commit it this week. I'll also
> think
> about applying a slightly less intrusive patch (not touching info_item and
> the updates code, at least -- suggestions are welcome) to -stable.
>
> --
> Mauro Giachero
>


More information about the sbopkg-users mailing list