I see that xz is available for EL-5, but not for EL-4. Would it be possible to branch xz for EL-4 as well?
It would be useful to have that utility available there as well. I did try downloading the el.5 source rpm, but it has a dependency on xz which keeps me from trying to build it there.
FWIW, the upstream source did compile OK on an EL-4 machine I have.
Thanks!
Dave
On Fri, Feb 12, 2010 at 12:48:27PM -0800, David Rees wrote:
I see that xz is available for EL-5, but not for EL-4. Would it be possible to branch xz for EL-4 as well?
It would be useful to have that utility available there as well. I did try downloading the el.5 source rpm, but it has a dependency on xz which keeps me from trying to build it there.
FWIW, the upstream source did compile OK on an EL-4 machine I have.
Are you a Fedora packager? I'm the EL-5 package maintainer for xz and I'd be happy to have you maintain it in EL-4. I don't have any EL-4 boxes so I'm not too motivated to do so myself but I have absolutely no objection with someone else doing it.
PS: The xz source is distributed as both tar.gz and tar.xz. We're using the xz compressed tarball which is why you can't build the rpm directly. For bootstrapping into EL-4, you can first build a release with the tar.gz tarball and then build the next release with tar.xz.
-Toshio
On Fri, Feb 12, 2010 at 3:35 PM, Toshio Kuratomi a.badger@gmail.com wrote:
On Fri, Feb 12, 2010 at 12:48:27PM -0800, David Rees wrote:
I see that xz is available for EL-5, but not for EL-4. Would it be possible to branch xz for EL-4 as well?
It would be useful to have that utility available there as well. I did try downloading the el.5 source rpm, but it has a dependency on xz which keeps me from trying to build it there.
FWIW, the upstream source did compile OK on an EL-4 machine I have.
Are you a Fedora packager?
Unfortunately, no, I'm not.
I'm the EL-5 package maintainer for xz and I'd be happy to have you maintain it in EL-4. I don't have any EL-4 boxes so I'm not too motivated to do so myself but I have absolutely no objection with someone else doing it.
Well, I was hoping that this branch would be next to no trouble for you, but otherwise, I'll read the docs to see what it takes to become a packager. Although with just me having just a handful of machines still running EL-4 it may be easier to just build from source although it would give me the opportunity to package other RPMs in the future...
PS: The xz source is distributed as both tar.gz and tar.xz. We're using the xz compressed tarball which is why you can't build the rpm directly. For bootstrapping into EL-4, you can first build a release with the tar.gz tarball and then build the next release with tar.xz.
Yes, I figured as much. Thanks for the tip. Sure I can't talk you into branching xz for EL-4? :-)
Thanks!
Dave
On Fri, Feb 12, 2010 at 05:24:18PM -0800, David Rees wrote:
On Fri, Feb 12, 2010 at 3:35 PM, Toshio Kuratomi a.badger@gmail.com wrote:
I'm the EL-5 package maintainer for xz and I'd be happy to have you maintain it in EL-4. I don't have any EL-4 boxes so I'm not too motivated to do so myself but I have absolutely no objection with someone else doing it.
Well, I was hoping that this branch would be next to no trouble for you, but otherwise, I'll read the docs to see what it takes to become a packager. Although with just me having just a handful of machines still running EL-4 it may be easier to just build from source although it would give me the opportunity to package other RPMs in the future...
PS: The xz source is distributed as both tar.gz and tar.xz. We're using the xz compressed tarball which is why you can't build the rpm directly. For bootstrapping into EL-4, you can first build a release with the tar.gz tarball and then build the next release with tar.xz.
Yes, I figured as much. Thanks for the tip. Sure I can't talk you into branching xz for EL-4? :-)
Nope, but I'll be happy to act as your sponsor! You can start learning about packaging rpms by looking at the srpm and I'll walk you through the two building steps to change the EL-5 package to use a tar.gz tarball, and then change it back to tar.xz afterwards.
If you're on IRC.freenode.net, I can help you in real-time (although not so much in the next two weeks -- I'll mostly be away at pycon those weeks).
If you're interested, let me know.
-Toshio
On Fri, Feb 12, 2010 at 5:45 PM, Toshio Kuratomi a.badger@gmail.com wrote:
On Fri, Feb 12, 2010 at 05:24:18PM -0800, David Rees wrote:
Yes, I figured as much. Thanks for the tip. Sure I can't talk you into branching xz for EL-4? :-)
Nope, but I'll be happy to act as your sponsor! You can start learning about packaging rpms by looking at the srpm and I'll walk you through the two building steps to change the EL-5 package to use a tar.gz tarball, and then change it back to tar.xz afterwards.
If you're on IRC.freenode.net, I can help you in real-time (although not so much in the next two weeks -- I'll mostly be away at pycon those weeks).
If you're interested, let me know.
I've done a bit of packaging on my own systems so I have a bit of knowledge about building / maintaining RPMs - should I just go ahead and build a .spec and .src.rpm with the .gz src and submit a Package Review Request and let you know so you can sponsor me?
Or do I just need to build the .gz version to bootstrap my EL-4 system and then verify that that .xz version builds afterwards and submit that? How do the build systems handle that chicken and egg problem?
-Dave
epel-devel@lists.fedoraproject.org