Re: Migrating sub-package to a different package: How to resolve file conflicts

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

 



On Wed, Jun 14, 2017 at 12:22:53PM +0200, Vít Ondruch wrote:
> IMO, the latest package should be always non-versioned one and versioned
> should be only the compat packages.
> E.g. the llvm package is always the latest, shipping llvm 4.0 ATM and
> llvm3.9 should be compat package, shipping the previous version. Once
> new version is released, lets say llvm 5.0, the non-versioned llvm
> should be migrated to that version and compat llvm4.0 should be introduced.

All other things aside, this is pragmatically easier, because creating
a new package4 or package5 triggers a new package review.


-- 
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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