Re: jansi 2.x and jline 3.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I believe the right thing to do would be to move to jline 3 for package
'jline' in rawhide and better, and perhaps keep jline2 as a
compatibility package[1], like jline1 was at some point. That is, if
some packages won't work with jline 3.

%mvn_compat_version macro might be helpful. See for example:
https://src.fedoraproject.org/rpms/jline1/blob/f31/f/jline1.spec#_95

HTH,
Severin

[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/Java/#_compatibility_packages


On Sun, 2020-12-13 at 20:43 -0700, Jerry James wrote:
Hi all,

I would like to keep jacop in Fedora.  It is in danger of removal, due
to the orphaning of scala.  I've taken a look at keeping scala in
Fedora, and updating it to its most recent version; see:

https://copr.fedorainfracloud.org/coprs/jjames/scala/

One issue is that recent scala needs jline 3.x (we have 2.x in
Rawhide), and jline 3.x needs jansi 2.x (we have 1.x in Rawhide).
Neither is backwards compatible with its previous major version.  I
have made jansi 1.x/2.x and jline 2.x/3.x parallel installable, but
there is still at least one issue.  The current jansi package
Provides:

jansi = 1.18-5.fc33
mvn(org.fusesource.jansi:jansi) = 1.18
mvn(org.fusesource.jansi:jansi-project:pom:) = 1.18
mvn(org.fusesource.jansi:jansi:pom:) = 1.18
osgi(org.fusesource.jansi) = 1.18.0

The jansi2 package on COPR Provides:

jansi2 = 2.1.0-1.fc34
jansi2(x86-64) = 2.1.0-1.fc34
libjansi.so()(64bit)
mvn(org.fusesource.jansi:jansi) = 2.1.0
mvn(org.fusesource.jansi:jansi:pom:) = 2.1.0
osgi(org.fusesource.jansi) = 2.1.0

There is overlap between the Provides, albeit with different version
numbers.  How should this be handled?  I guess that packages that need
version 1.x would have to include "BuildRequires: jansi < 2" and
"Requires: jansi"?

Also, is it better to keep the existing jansi and jline packages, and
add jansi2 and jline3 packages as I have done on COPR, or would it be
better to add jansi1 and jline2 packages containing the current
contents of jansi and jline, and then move jansi and jline to their
latest versions?

I appreciate any thoughts anyone has on the matter.  Regards,
-- 
Jerry James
http://www.jamezone.org/
_______________________________________________
java-devel mailing list -- java-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to
java-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/java-devel@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
java-devel mailing list -- java-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to java-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/java-devel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Red Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux