Hello,
Bernhard: The 'par' package itself still seems advantageous because it
can create PAR (or PAR1 if you rather) volumes. These are very fast
to create, with the trade off that they consume a considerable amount
of disk space. No one is maintaining upstream because it's basically
complete at this point, as far as I understand. I suppose another
reason is 'because we can' for open source software and there is very
little overhead with maintenance of these packages.
Carlos: The 'par2cmdline' package can verify both PAR/PAR2 volumes.
Therefore, 'par' would not be needed if you only wished to verify.
Even though the answer is 'yes' to your question, I believe the 'par'
package should still remain because one might want to create PAR
volumes (for speed of creation/nostalgia/research/etc).
There many reasons to choose par2 over par and they are listed in the
par2cmdline README if you would like to scan over them:
https://github.com/Parchive/par2cmdline/blob/master/README
As far as maintaining it and keeping it building I am happy to do so
(and I have been assigned as maintainer of both in the Archive devel
project already). It should be pretty trouble free to maintain for
years to come.
Thanks for the input!
Doug
On Thu, May 23, 2019 at 7:44 AM Carlos E. R.
On 23/05/2019 09.38, Bernhard M. Wiedemann wrote:
On 22/05/2019 16.53, Doug Miller wrote:
The original SourceForge Parchive project has been inactive since November 9, 2010. The par2cmdline github project has active development.
isnt this an indicator that the original par should be dropped, because nobody is maintaining it anymore? Reminds me of uClibc-ng [1]
The remaining question then is about the naming of the par2 package
Or is 'par' still useful for some cases and someone is willing to keep it building and address issues?
I'll pose another question. Can data saved with par long ago be recovered with par2?
If the answer is no, then par is still needed, as is (ie, with whatever bugs it has).
-- Cheers / Saludos,
Carlos E. R. (from 15.0 x86_64 at Telcontar)
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org