Just to illustrate what this is about, these are 3 PR trying to fix
the branches for next RHEL:
https://src.fedoraproject.org/rpms/rubygem-ruby-rc4/pull-request/1
https://src.fedoraproject.org/rpms/rubygem-Ascii85/pull-request/1
https://src.fedoraproject.org/rpms/rubygem-nokogiri/pull-request/1
Non of them is correct, because they are not maintained. If there
were no branches, it would be much better.
V.
Dne 20.1.2018 v 12:27 Igor Gnatenko napsal(a):
Hello,
I know that many of you like to have just one branch which builds
everywhere
(starting from el6), but this really slows down development of
Fedora for many
years. Let me show some examples:
* File-triggers are not supported by el6/el7 RPM, so every package
which has
icons should have some number of scriptlets conditionalized by
%if 0%{?rhel}
&& 0%{?rhel} <= 7.
* Rich dependencies are not supported by el6/el7 RPM and YUM, so
anyone who
wants to use them need to have same conditionals.
* Some of dependency generators do not exist on el*, so instead of
having
BuildRequires: python3dist(foo) you need to wrap it with
conditions again and
I'm working on change proposal which eliminates need of writing
runtime
requirements, so one more place of conditionals.
Given all these, it is very hard to get any new feature in
"production" because
everyone wants to support 10 years old thing (even if they don't
think so).
Even if people hope next version of EL will be better in this, it
doesn't mean
that el6/el7 can be fixed easily.
Why I'm writing this? I want to hear from you if you think it
would be good to
prohibit (or advise, or whatever mechanism would work) usage if
conditionals in
(at least) master branch to allow us to develop features faster.
Thoughts?
Suggestions?
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
|
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx