Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing tags/releases (2.102 and 2.106) #5

Open
M0ses opened this issue Jul 4, 2022 · 4 comments
Open

Missing tags/releases (2.102 and 2.106) #5

M0ses opened this issue Jul 4, 2022 · 4 comments

Comments

@M0ses
Copy link

M0ses commented Jul 4, 2022

It would be good to have tags/release aligned to the versions distributed with the perl5 core.
This would make linux packagers life much easier.

@pmqs
Copy link
Owner

pmqs commented Jul 14, 2022

Hey @manwar - sorry for the delay in responding.

I do try to keep the versions in sync as much as possible, but there are times when I do forget.

Does the rule of just going for the newest version available cause packaging problems for the Linux distros?

@M0ses
Copy link
Author

M0ses commented Jul 15, 2022

I cannot speak for other distributions than openSUSE/SUSE.

In openSUSE there are 2 packages which get built out of the official perl5 tarball (perl/perl-base).

All modules which are bundled with upstream/vanilla perl are in the package "perl".
IO::Compress also includes 2 scripts (streamzip/zipdetails) which conflict if you want to install e.g. perl-IO-Compress (CPAN module) with "perl"

Mixing multiple versions of IO::Compress (IMHO) is a bad idea and not maintainable. It might work in 99% or more, but it could create problems which nobody wants to debug.

So my idea was to keep the version of perl-IO-Compress-LZMA aligned to IO::Compress from the vanilla perl.

@pmqs
Copy link
Owner

pmqs commented Jul 15, 2022

Thanks for the useful feedback @M0ses

The thing that I can control are the versions of the various IO::Compress::* modules. My original intention was to always keep them in sync, but as you've seen I don't always succeed in that. Will try to deal with that going forward.

@M0ses
Copy link
Author

M0ses commented Jul 15, 2022

My original intention was to always keep them in sync

awesome

, but as you've seen I don't always succeed in that.

Remember: nobody is perfect! :-)

Will try to deal with that going forward.

This would be really a great, and I could offer that I would ping you if I don't find the tags again. ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants