Hi,
Would anyone object to me retiring the "xml-commons-apis12" package in F20?
It is a compatibility package that has been hanging around for years that provides an earlier version of the APIs provided by the "xml-commons-apis" package.
All packages that need these APIs should be requiring or buildrequiring xml-commons-apis instead. The last remaining package in F20 that used this package was axis and I have just committed a patch for the that allows it to build against the newer xml-commons-apis.
With no more packages in Fedora that depend on xml-commons-apis12 I would like to retire it for F20 and later.
Mat
Quoting Mat Booth (2013-08-07 12:48:02)
Hi,
Would anyone object to me retiring the "xml-commons-apis12" package in F20?
It is a compatibility package that has been hanging around for years that provides an earlier version of the APIs provided by the "xml-commons-apis" package.
All packages that need these APIs should be requiring or buildrequiring xml-commons-apis instead. The last remaining package in F20 that used this package was axis and I have just committed a patch for the that allows it to build against the newer xml-commons-apis.
With no more packages in Fedora that depend on xml-commons-apis12 I would like to retire it for F20 and later.
I'd say: just do it. The less old cruft we have the better. We all have enough work as it is. If any new package doesn't bother to update to new xml APIs...then it shouldn't even be added to Fedora.
On 7 August 2013 21:09, Stanislav Ochotnicky sochotnicky@redhat.com wrote:
Quoting Mat Booth (2013-08-07 12:48:02)
Hi,
Would anyone object to me retiring the "xml-commons-apis12" package in
F20?
It is a compatibility package that has been hanging around for years that provides an earlier version of the APIs provided by the
"xml-commons-apis"
package.
All packages that need these APIs should be requiring or buildrequiring xml-commons-apis instead. The last remaining package in F20 that used
this
package was axis and I have just committed a patch for the that allows it to build against the newer xml-commons-apis.
With no more packages in Fedora that depend on xml-commons-apis12 I would like to retire it for F20 and later.
I'd say: just do it. The less old cruft we have the better. We all have enough work as it is. If any new package doesn't bother to update to new xml APIs...then it shouldn't even be added to Fedora.
Done!
On 7 August 2013 21:09, Stanislav Ochotnicky sochotnicky@redhat.com wrote:
Quoting Mat Booth (2013-08-07 12:48:02)
Hi,
Would anyone object to me retiring the "xml-commons-apis12" package in
F20?
It is a compatibility package that has been hanging around for years that provides an earlier version of the APIs provided by the
"xml-commons-apis"
package.
All packages that need these APIs should be requiring or buildrequiring xml-commons-apis instead. The last remaining package in F20 that used
this
package was axis and I have just committed a patch for the that allows it to build against the newer xml-commons-apis.
With no more packages in Fedora that depend on xml-commons-apis12 I would like to retire it for F20 and later.
I'd say: just do it. The less old cruft we have the better. We all have enough work as it is. If any new package doesn't bother to update to new xml APIs...then it shouldn't even be added to Fedora.
--
Does anyone know how to contact guidograzioli? It would be great to retire maven2-common-poms too, but he isn't responding to the bugzilla ticket:
https://bugzilla.redhat.com/show_bug.cgi?id=887166
Mat
java-devel@lists.fedoraproject.org
-
Mat Booth -
Stanislav Ochotnicky