Re: Fedora 31 System-Wide Change proposal: Switch RPMs to zstd compression

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

 



On Fri, May 31, 2019 at 9:36 AM Nicolas Mailhot via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Le vendredi 31 mai 2019 à 02:15 +0200, Pavel Raiskup a écrit :
> On Thursday, May 30, 2019 10:38:25 AM CEST Miroslav Suchý wrote:
> > Dne 29. 05. 19 v 23:52 Josh Boyer napsal(a):
> > > If we did this, wouldn't it make it very difficult to use tools
> > > like
> > > mock on RHEL / CentOS 7 to build for Fedora 3x?
> >
> > Speaking of Mock:
> > Either the RPM on host need to understand the new
> > format/compression **or**
> > the packages in @buildsys group (including transitional deps) have
> > to be in
> > old format - then you can build for Fedora 3x using bootstrap
> > feature.
>
> I need to underline this, it would be really really really bad if we
> were
> not able to --installroot fedora chroots at least on RHEL 8.  How
> likely
> is a backport of zstd support into RPM in EL7+?

We should not been talking about rpm backports, so much of the
fedora/epel/el flow depends on rpm enhancements, new rpm versions
should be pushed by default to old streams after a year/six months of
proofing Fedora-side.

I'm quite sure all the efforts wasted working around old rpm
limitations in EL cost a lot more (including @RH) than the people that
would be needed to correct problems in case something slipped through
Fedora QA. It's done for Firefox and the amount of changes pushed to
Firefox is crazy compared to what happens rpm side.

You just forgot that Firefox while being important piece for desktop users is not used by anything. But everything depends on RPM. If you want new version of RPM, you need to also rebuild packages to ensure that they are generated with new RPM... And so on.

The non-rpm distributors are running circles around Fedora and EL, and
it's not because their binaries are better, their QA process more
solid, their core design easier to use, it's just that they make their
software deployments enhancements available timely and not after 5
years of procastination.

Right now any attempt to contribute modern rpm packaging starts with a
long list of “you could do X, but it’s not available yet, use Y
instead”. Who actually expects to attract new contributors this way?

--
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux