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

Re: partman, growlight, discoverable partitions, and fun




> On Sep 27, 2021, at 3:41 PM, Luca Boccassi <bluca@debian.org> wrote:
> 
> On Mon, 2021-09-27 at 15:18 +0200, John Paul Adrian Glaubitz wrote:
>> 
>>>> On Sep 27, 2021, at 2:25 PM, Luca Boccassi <bluca@debian.org> wrote:
>>> 
>>> Even if that interpretation would work as an excuse to never do
>>> anything, and I'm not really sure it does, this specification has been
>>> published in 2014 [0] so even by Debian standard it's old stuff.
>> 
>> That’s not what I said so. You’re trying to dismiss my opinion as completely invalid now by trying to frame it such that I am against progress. I am not.
> 
> You dismissed it because it's "new technology":
> 
>> Not for me, though. Debian has always followed the philosophy to be a universal
>> operating system, which also meant that we can't (immediately) use all the new
>> technologies and features that other distributions or upstream projects develop.

You’re reducing my argument to the word “new” which is definitely not my point. As you can see from the rest of my message my primary point is that Debian follows a different philosophy meaning that we don’t always adopt technologies that other distributions use.

Fedora and openSUSE are much more similar to each other than Debian is to both.

> I simply pointed out that it's a 7 years old spec that saw an entire
> LTS Debian version (8, we are now at 11) being released and EOL'ed
> since the time it was published. If this is too new to consider, then
> so are all Debian releases newer than Wheezy.

Yes, but the age was never my argument. My argument was that replacing such a fundamental software component like the partitioning tool in an installer is something that has to be justified by technical merits and by weighing pros and cons against each other.

The fact that’s it’s newer or has the single feature X is not sufficient in my opinion. Especially when there is no proof yet that getting support for discoverable partitions justifies the loss of features that parted has.

>>> It's
>>> older than Debian Jessie, which was EOL'd last year. If libparted can't
>>> keep up with 7 years old stuff that in the meantime was implemented in
>>> util-linux's (which is a truly universal tool) in 2014, gdisk in 2019,
>>> and so on, then to me it sounds like a tool in maintenance mode:
>>> perfectly fine and adequate for existing tools and programs, but not
>>> quite the best choice for new tools developed from scratch.
>> 
>> Whether a tool that was developed new from scratch is automatically better is not a given. The burden of proof is on the person trying to introduce the new software, not on the people maintaining the current set of software.
>> 
>> And claiming that parted is in pure maintenance mode is not true either. It has a paid developer working on the project and is receiving updates and improvements.
>> 
>> Whether growlight is better and more suitable for Debian needs to be technically proven, not just by arguing that it’s the newer project.
>> 
>> Adrian
> 
> Of course. But jumping in and saying "you should use X instead of Y",
> you can't pretend that nobody asks questions such as "ok, but does libX
> support this very much related and relevant 7 years old specification
> that other comparable tools support", no matter how awkward it is for
> libX.

I was not the one that was making this request, it was Nick. I’m perfectly fine with the status quo.

Again, the party introducing the new solution should provide the arguments to convince the maintainers of the existing solution.

For example, a convincing argument would be a demonstration installation ISO which let’s others interested in the project test it and check whether it delivers the improvements that were promised.

I don’t think that this is such an extraordinary requirement to ask for.

Also, I would be interested to know what approaches are currently used in Fedora, Arch, Gentoo and openSUSE (I will check that later myself when I’m back at the computer).

Adrian 

Reply to: