Re: Announcing the existance of a separate python-bytesize package to handle the Size functionality of blivet.

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

 






----- Original Message -----
> From: "Vratislav Podzimek" <vpodzime@xxxxxxxxxx>
> To: "Discussion of Development and Customization of the Red Hat Linux Installer" <anaconda-devel-list@xxxxxxxxxx>
> Sent: Thursday, February 19, 2015 9:58:50 AM
> Subject: Re: Announcing the existance of a separate python-bytesize package	to handle the Size functionality of
> blivet.
> 
> On Thu, 2015-02-19 at 08:30 -0500, Anne Mulhern wrote:
> > The two drawbacks to making it a separate package are:
> > 1) The tasks involved in making a separate package are a big pain.
> > 2) Moving translations is going to be a bit tricky.
> > 
> > But the advantage is that it can be used outside of blivet.
> > There is nothing about it which is really blivet specific,
> > and I think that it should be made possible to use w/out
> > requiring blivet.
> A subpackage built from the blivet sources doesn't have to depend on
> blivet at all. And it can even have a totally unrelated name.
> 

The idea of a sub-package is alluring...because this package
maintainer process is so miserable right now.

But I think that bytesize can be viewed as entirely distinct
from blivet, and it doesn't seem to be the purpose of subpackages
to contain potentially completely independent and far more general
packages (based on what the old Maximum RPM book has to say).

> > 
> > I don't mind if it's usable only from Python. I feel like its
> > better to assist Python programmers than to enable C programmers,
> > who probably wouldn't appreciate it's facilities anyway.
> > It makes use of Python facilities like unbounded ints
> > and the Decimal class in its implementation. These are not so easy
> > to come by in C.
> That's exactly why it would be really useful in C too. e.g. in udisks,
> Cockpit or whatever non-python project.
> 

When these people come clamouring for a C version of bytesize, I will listen politely,
and try to help them all I can. But my natural diffidence says that rewriting
bits of some rather sophisticated Python libraries and so forth in
C is bound to result in some mistakes. I honestly think that the
people who developed the Decimal class know way more about numeric
representations than I do, and I know way more than the average programmer.
The cost of even minor development and maintenance will go up an order of magnitude
if this thing is rewritten in C; I'm in no hurry to pay that cost, and the
startup cost of rewriting, until it is shown to be necessary or very desirable.

> --
> Vratislav Podzimek
> 
> Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
> 

- mulhern

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux