Hi,
as some of you are aware jakarta-commons changed name to apache-commons some time ago. We should probably start process of renaming these packages in Fedora as well to match upstream.
I made a list of -commons components that do not depend on other -commons. This was done with a crude grep of checked out sources so there might be omissions). Owners of packages included:
jakarta-commons-codec - mbooth jakarta-commons-launcher - mbooth jakarta-commons-logging - mbooth jakarta-commons-pool - mbooth
jakarta-commons-daemon - pcheung jakarta-commons-io - pcheung jakarta-commons-lang - pcheung jakarta-commons-net - pcheung
jakarta-commons-collections - devrim
jakarta-commons-compress - red
jakarta-commons-el - fnasser
Starting with these packages should make it easier to continue with the rest (because for those we can already start using new names in Requires).
Any ideas/notes are welcome,
2010/5/4 Stanislav Ochotnicky sochotnicky@redhat.com:
Hi,
as some of you are aware jakarta-commons changed name to apache-commons some time ago. We should probably start process of renaming these packages in Fedora as well to match upstream.
Hi,
Indeed, this has been on my TODO list for a while. I will get to this Real Soon Now(tm), I promise :-)
Regards, Mat
PS. You wanted mbooth@fedoraproject.org, not @redhat.com ;-)
On 05/04/2010 02:31 PM, Mat Booth wrote:
2010/5/4 Stanislav Ochotnicky sochotnicky@redhat.com:
Hi,
as some of you are aware jakarta-commons changed name to apache-commons some time ago. We should probably start process of renaming these packages in Fedora as well to match upstream.
Hi,
Indeed, this has been on my TODO list for a while. I will get to this Real Soon Now(tm), I promise :-)
Perfect
I opened a bug https://bugzilla.redhat.com/show_bug.cgi?id=588764 to track progress. When you create package review requests please add their bz# to depends on this bug.
I will also create wiki page so that everyone will know current status of all jakarta-commons packages (renamed/on review/waiting for deps/etc.). Will post link later on
PS. You wanted mbooth@fedoraproject.org, not @redhat.com ;-)
Yes I noticed two things after I sent the email: 1. someone (TB or mailing list perhaps) screwed up CC (there were 6 people in there when I was sending the mail, only 3 are present in the message on the mailing list)
2. some people had old emails because they were automatically added from LDAP for me. Didn't realize they were deprecated. I'm crossing my fingers hoping they are reading the mailing list :-)
Regards,
On 05/04/2010 10:43 AM, Stanislav Ochotnicky wrote: I will also create wiki page so that everyone will know current status of all jakarta-commons packages (renamed/on review/waiting for deps/etc.). Will post link later on
As promised here it is: https://fedoraproject.org/wiki/JakartaCommonsRename
Also reminder for the tracker bug: https://bugzilla.redhat.com/show_bug.cgi?id=588764
We should be able to paralelize after first few packages are reviewed.
Are we going to do
Provides: jakarta-commons-X
To keep from redoing all of the dependency packages?
On 05/04/2010 11:58 AM, Stanislav Ochotnicky wrote:
On 05/04/2010 10:43 AM, Stanislav Ochotnicky wrote: I will also create wiki page so that everyone will know current status of all jakarta-commons packages (renamed/on review/waiting for deps/etc.). Will post link later on
As promised here it is: https://fedoraproject.org/wiki/JakartaCommonsRename
Also reminder for the tracker bug: https://bugzilla.redhat.com/show_bug.cgi?id=588764
We should be able to paralelize after first few packages are reviewed.
-- java-devel mailing list java-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/java-devel
On 4 May 2010 19:26, Adam Young ayoung@redhat.com wrote:
Are we going to do
Provides: jakarta-commons-X
To keep from redoing all of the dependency packages?
I would say that yes, the standard obsoletes/provides policy should apply as this will also prevent conflicts from JPackage installed packages.
java-devel@lists.fedoraproject.org