On Sun, Nov 23, 2008 at 6:05 PM, Jud <jud@judfilm.net> wrote:
On Wed, 5 Nov 2008 11:38:04 -0600 "Aaron Griffin" <aaronmgriffin@gmail.com> wrote:
On Wed, Nov 5, 2008 at 11:35 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Wed, 5 Nov 2008 10:25:08 -0600 schrieb "Aaron Griffin" <aaronmgriffin@gmail.com>:
If no one minds, I think I will rename pkg-config today. Andy, do you care if I do that?
I wouldn't spend time on that until there's an update coming. But if you have the time go on and do it.
But please add provides=('old-fooname') wherever you make changes to not break packages from community repos and AUR. That saves us also the rebuilds.
Is it enough to "svn rename/mv foo-new" and commit or do we have to svn del/add the pkg?
No a rename is preferred as it should, in theory, retain history from when it was named something else.
Just so this is not forgotten about
pkconfig > pkg-config lzo2 > lzo libsigc++2.0 > libsigc++ gimp-help-2 > gimp-help freetype2 > freetype
iproute > iproute2 sqlite3 > sqlite
Any of the maintainers interested in making this change, don't forget to add replaces/provides for the previous package. Or skip the provides and rebuild all deps, but that seems messy.
kernel26 > kernel
Lets hold off on this one for a bit, as they were talking about redoing kernel versioning, and that might be a big issue.