[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google
  Web www.spinics.net

Packaging from JPackage spec - any required changes to license, coordinating with commons rename?



Hi,

I am re-packaging html-unit from JPackage source to Fedora target
rawhide for submission for sponsorship.


1) JPackage requires retention of the comments including copyright and
license (see Appendix to e-mail).
Do I need to do any modifications to it?

2) Following commons packages are required:

BuildRequires:  jakarta-commons-codec >= 0:1.3
BuildRequires:  jakarta-commons-collections32
BuildRequires:  jakarta-commons-fileupload >= 0:1.2.1
BuildRequires:  jakarta-commons-httpclient >= 0:3.0.1
BuildRequires:  jakarta-commons-io >= 0:1.3.1
BuildRequires:  jakarta-commons-lang24
BuildRequires:  jakarta-commons-logging >= 0:1.1

Packaging rename task specifies Rawhide Fedora 14 as target rename release:
https://fedoraproject.org/wiki/JakartaCommonsRename

Should I wait for rename of these for Rawhide Fedora 14 to appache-commons-...
before submiting package for review, or should I target earlier release?

Please advise.
--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel

[Home]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Red Hat 9 Bible]     [Fedora Bible]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

Powered by Linux

Google
  Web www.spinics.net