Re: Over 40% of the 6.0 RPM's, especially SRPM's, are not RHEL 5 compatible

Great. I'd be happy with the SRPM's for now: building the RPM's under
RHEL 5 is..... an adventure, due to the age of the Java components
under RHEL.

On Fri, Apr 2, 2010 at 8:30 AM, Jason Corley <[email protected]> wrote:
> since 6.0 isn't a release yet I don't think it's a huge concern, but
> we should definitely rebuild all of these packages prior to 6.0 even
> going beta... we can't leave a large portion of functionality
> unavailable to one of our supported platforms.
> Jason
>
> On Fri, Apr 2, 2010 at 8:06 AM, Nico Kadel-Garcia <[email protected]> wrote:
>> After some recent discussion about which RPM versions were used to
>> build the 6.0 software, and some very helpful explanation of the use
>> of the '%{rpmversion}' option for detecting which are compatible with
>> older releases, I've noticed that approximately 40% of the SRPM's in
>> the Jpackage 6.0 release are not installable under RHEL 5.
>>
>> I realize it's a pain in the neck, and potentially begging for version
>> skew. But how bad would it be to set up at least an SRPM directory
>> with those SRPM's rebuilt, perhaps with a slightly updated "Release:"
>> field to avoid confusion about the checksums of the SRPM packages. I
>> admit that I, personally, like using this syntax.
>>
>>    Release: 1%{?dist}
>>
>> That way, I can set "dist" locally in .rpmmacros or as an rpmbuild
>> option to set an OS or configuration environment specific settting. It
>> might be useful here and in general.
>> _______________________________________________
>> JPackage-discuss mailing list
>> [email protected]
>> https://www.zarb.org/mailman/listinfo/jpackage-discuss
>>
> _______________________________________________
> JPackage-discuss mailing list
> [email protected]
> https://www.zarb.org/mailman/listinfo/jpackage-discuss
>