[Solved] Patch for idle3-tools

Package aur/idle3-tools (0.9.1-1) installs a binary under /sbin and is thus affected by the recent /usr/bin consolidation; indeed, it was one of a handful of packages on my system that I uninstalled so I could do the upgrade.

I have flagged the package and no doubt the maintainer will attend to it in due course, but to try and help out a bit I include below the changes necessary to make the package install in a post-consolidation Arch environment. Cursory searches of the source do not suggest the presence of any (other) hard-coded paths, and the binary appears to be operable from the new location, so it's only a build issue.

(2) PKGBUILD.diff (to make a new PKGBUILD) -- In addition to including the above patch, it also corrects issues identified by namcap (full package name appearing in description, and an apparent dependency on glibc)

As this is the first time I have actually constructed a patch myself and made it available, any (constructive) feedback is welcome; I tried to make as few changes as possible to the original files, so apologies if I missed correcting/adjusting things that should have been changed as well.

I will of course add a comment to the package page in AUR noting this topic.

Re: [Solved] Patch for idle3-tools

I was going to tell you to use the "./configure" step to do this, but it appears that this source only have a makefile. So I guess it would indeed be the way to do this. So I think in the AUR comments, you should create a tarball and then upload it to some file hosting site and link to it from there. It would just make things much easier for anyone trying to get this package.

Looking over what you have done, I would say that this is pretty a-okay.

Thank you . I will take note of your point about parameters to ./configure, since there are four other packages I intend to look at (hopefully over the course of the next few days) and I can certainly see some of them having a configure step.

WonderWoofy wrote:

...I think in the AUR comments, you should create a tarball and then upload it to some file hosting site and link to it from there. It would just make things much easier for anyone trying to get this package.

I don't currently have an account on such a site unfortunately, but will have a look at this after I look into the other packages (if however anyone else is reading this in the interim, does have such an account and is feeling particularly energetic, feel free).

Re: [Solved] Patch for idle3-tools

There are those free single public file hosting sites that yu can use. Otherwise, I would say that since the package has not been updated since it was first uploaded, you should email the maintainer and see if you get a response. I doubt that you will since it was uploaded and last updated in 2011. If you don't get a response for two weeks you can then email aur-general and have the package orphaned so that you can adopt it.

Re: [Solved] Patch for idle3-tools

Good point. I admit I've never looked into such services, but if I'm going to help out with things like this I probably should . I'll do some research, unless there are some particular services you (and/or the ArchLinux community in general) recommend...?

WonderWoofy wrote:

Otherwise, I would say that since the package has not been updated since it was first uploaded, you should email the maintainer and see if you get a response. I doubt that you will since it was uploaded and last updated in 2011. If you don't get a response for two weeks you can then email aur-general and have the package orphaned so that you can adopt it.

Fair enough. The maintainer updated another package in AUR seven weeks ago, so there's reason to believe that they'll respond. I'll give them a bit of time to do so (as there's a workaround, per this thread), and will then follow through as you suggest; I'll also post updates here for anyone interested.

The lack of updates is likely due to upstream not having issued a new version since the package was uploaded (and the last commit to upstream is dated 24 January 2012); it's possible the tool is unmaintained upstream, though it does seem to get several hundred downloads each month (per SourceForge's stats) and there aren't lots of complaints plastered all over the discussions/bugs, so who knows?