Hi all,
In trying to be consistent with Arch's standard of naming packages the same as upstream, I have notice two packages that will need attention.
lzo2 ==> lzo pkgconfig ==> pkg-config
The old lzo was only required by transcode which is now fixed. Can the old lzo be moved into unsupported?
lzo2 (required by): * archboot * lzop * mkvtoolnix * openvpn * transcode
There seems to be a few packages that have 'pkgconfig' as a 'makedepends', this could easily be a one-off fix as needed when that particular package needs to be updated.
pkgconfig (required by): * dssi * python-vpython
This will be the last time I attach full PKGBUILDs, I'm off to try and learn SVN.
Thanks.
On Fri, Oct 17, 2008 at 12:05 AM, Jud jud@judfilm.net wrote:
In trying to be consistent with Arch's standard of naming packages the same as upstream, I have notice two packages that will need attention.
lzo2 ==> lzo pkgconfig ==> pkg-config
I'd agree with this. Andy, Tom, do you have any problems doing this? Does anyone with the time want to tackle this? It should be straightforward.
The old lzo was only required by transcode which is now fixed. Can the old lzo be moved into unsupported?
Let's delete it. It has no 'Required By' according to the web interface.
lzo2 (required by):
- archboot
- lzop
- mkvtoolnix
- openvpn
- transcode
pkgconfig (required by):
- dssi
- python-vpython
This should be an easy set of rebuilds. As for makedepends, we can always sed them and commit, without a rebuild of the package
On Mon, 20 Oct 2008 11:49:05 -0500 "Aaron Griffin" aaronmgriffin@gmail.com wrote:
On Fri, Oct 17, 2008 at 12:05 AM, Jud jud@judfilm.net wrote:
In trying to be consistent with Arch's standard of naming packages the same as upstream, I have notice two packages that will need attention.
lzo2 ==> lzo pkgconfig ==> pkg-config
I'd agree with this. Andy, Tom, do you have any problems doing this? Does anyone with the time want to tackle this? It should be straightforward.
The old lzo was only required by transcode which is now fixed. Can the old lzo be moved into unsupported?
Let's delete it. It has no 'Required By' according to the web interface.
lzo2 (required by):
- archboot
- lzop
- mkvtoolnix
- openvpn
- transcode
pkgconfig (required by):
- dssi
- python-vpython
This should be an easy set of rebuilds. As for makedepends, we can always sed them and commit, without a rebuild of the package
Just wanted to give this a nudge.
Also, I have found some more: libsigc++2.0 gimp-help-2 freetype2
Thanks.
On Wed, Nov 5, 2008 at 4:15 AM, Jud jud@judfilm.net wrote:
On Mon, 20 Oct 2008 11:49:05 -0500 "Aaron Griffin" aaronmgriffin@gmail.com wrote:
On Fri, Oct 17, 2008 at 12:05 AM, Jud jud@judfilm.net wrote:
In trying to be consistent with Arch's standard of naming packages the same as upstream, I have notice two packages that will need attention.
lzo2 ==> lzo pkgconfig ==> pkg-config
I'd agree with this. Andy, Tom, do you have any problems doing this? Does anyone with the time want to tackle this? It should be straightforward.
The old lzo was only required by transcode which is now fixed. Can the old lzo be moved into unsupported?
Let's delete it. It has no 'Required By' according to the web interface.
lzo2 (required by):
- archboot
- lzop
- mkvtoolnix
- openvpn
- transcode
pkgconfig (required by):
- dssi
- python-vpython
This should be an easy set of rebuilds. As for makedepends, we can always sed them and commit, without a rebuild of the package
Just wanted to give this a nudge.
Also, I have found some more: libsigc++2.0 gimp-help-2 freetype2
Thanks.
If no one minds, I think I will rename pkg-config today. Andy, do you care if I do that?
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?
-Andy
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.
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 kernel26 > kernel
Cheers Jud
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.
On Wed, 26 Nov 2008, Aaron Griffin wrote:
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.
I'll make the 'gimp-help-2 > gimp-help' change at the next update.
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.
On Wed, 26 Nov 2008 18:19:28 -0500 (EST) Eric Bélanger belanger@ASTRO.UMontreal.CA wrote:
On Wed, 26 Nov 2008, Aaron Griffin wrote:
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.
Any news on lzo and the others?
arch-dev-public@lists.archlinux.org