On Tue, Dec 6, 2011 at 11:45 AM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Tue, Dec 6, 2011 at 9:01 AM, Dan McGee <dpmcgee@gmail.com> wrote:
On Tue, Dec 6, 2011 at 1:27 AM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
I also did other minor change to the package: - Update license, Add file depends, Add missing hook scripts, Add python2 and ruby optdepends for the hook scripts, Clean up PKGBUILD, Remove old patches
What about svnmerge.py? This has been dead upstream for some time; we needed it for our repo scripts at one time but that ship sailed long ago [1]. Can we stop shipping it?
Sure unless there are some objections. Should I release a new -2 package with that change or just remove it from trunk so it'll get remove next time the package is updated?
I don't have any problem with just doing it on trunk- not a rush thing, just noticed we've had this old script hanging around for a while and I'm not even sure it still works as SVN has had mergeinfo integrated for a long time at this point. -Dan