From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Problem with updating ddrescue addon Date: Tue, 02 Feb 2021 14:17:10 +0000 Message-ID: <43174D70-6B36-4F71-B4B2-633FEBDFA28D@ipfire.org> In-Reply-To: <7a9be9b5-81bc-6b21-66bd-42c1f4ea063a@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5442595424828797116==" List-Id: --===============5442595424828797116== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, Sorry for my late reply. > On 31 Jan 2021, at 11:41, Adolf Belka wrote: >=20 > Hallo all, >=20 >=20 > I saw that ddrescue addon was a version from 2010 so I thought it was about= time to be updated. However since 2013 gnu has only been using lzip for the = tarballs and stopped providing gzip versions. >=20 > IPFire does not have lzip available at the moment. >=20 > The options seem to me to be:- >=20 > - remove ddrescue from the addon list This is an option, since it does not seem to be the most popular add-on. On t= he other hand, it does not cause us any trouble, so I would vote for keeping = it. > - leave ddrescue at the 2010 version - v1.12 That would be a bad choice, because we do not want to ship outdated software. > - update ddrescue to the last .gz tarball version in 2012 - v1.16 Again, this would be outdated. > - build lzip into the IPFire build system and update to latest ddrescue= version from March 2020 - v1.25 I would vote for this. There is seems to be a lot of chaos with the compressi= on algorithms right now. Gzip is outdated and does not compress very well, bz= ip2 is in the same situation. XZ compresses well, but it quite slow. LZMA was= a stepping stone to XZ. Now there is Zstandard, lzip and I have even seen tarballs being compressed w= ith lzo. They all seem to be have their individual advantages and disadvantag= es, but ultimately we will have to use what the maintainers of upstream softw= are chose to go with. Sooner or later we will have more packages using lzip. > should it go into the toolchain where the other compression pac= kages seem to be (how to do that?) Since we do not have anything in the toolchain stage yet that is requiring it= , I would suggest building it as a normal package and do so as early as possi= ble. It should not have any dependencies. > should it go into the build part of IPFire Yes :) > Looking through the changelog from v1.13 to 1.25 there are a lot of new opt= ions added but also some changes to the code itself that look to be fixing pr= oblems. I can't easily see how important these are. No changes have been mark= ed as critical bug fixes or even marked as a bug fix. >=20 > My view would be to update to the latest version or remove ddrescue from th= e addons, as 11 years old seems a long time in computing terms. Ancient :) Do we have more of those? Thank you for looking into this. It looks like ddrecuse was a package that I = simply have forgotten about. > I am open to taking any guidance on the best approach for this. Did I answer your questions? Best, -Michael >=20 > Regards, >=20 > Adolf. >=20 --===============5442595424828797116==--