i just did a sync and and world update, and app-arch/par was updated from
version 1.1 to version 2.0.3. problem is, this isn't a version bump - it's a
totally different app. the 1.1 ebuild merged a program called 'par' that
created and could verify/repair using PAR v1 files. the 2.0.3 ebuild merges a
program called 'par2cmdline' that does the same thing, only it handles PAR v2
files. it claims to have the ability to verify/repair using PAR v1 files, but
it cannot (as far as i am able to determine) create PAR v1 files. PARv2 hasn't
really caught on yet all that well, and a lot of people (myself included) still
use PARv1 when posting binaries to usenet. with this version bump i am unable
to do so without removing the new useless symlinks in /usr/bin (par, parcreate,
parrecover, parverify), and downloading and manually compiling and installing
the old par package.
i just did a sync and and world update, and app-arch/par was updated from
version 1.1 to version 2.0.3. problem is, this isn't a version bump - it's
a totally different app. the 1.1 ebuild merged a program called 'par' that
created and could verify/repair using PAR v1 files. the 2.0.3 ebuild merges
a program called 'par2cmdline' that does the same thing, only it handles
PAR v2 files. it claims to have the ability to verify/repair using PAR v1
files, but it cannot (as far as i am able to determine) create PAR v1 files.
PARv2 hasn't really caught on yet all that well, and a lot of people (myself
included) still use PARv1 when posting binaries to usenet. with this version
bump i am unable to do so without removing the new useless symlinks in /usr/bin
(par, parcreate, parrecover, parverify), and downloading and manually compiling
and installing the old par package.
