On Mon, Sep 3, 2018 at 8:02 AM Adam Samalik <asamalik@xxxxxxxxxx> wrote: > > > > On Mon, Sep 3, 2018 at 1:57 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: >> >> On Mon, Sep 3, 2018 at 1:32 AM Adam Samalik <asamalik@xxxxxxxxxx> wrote: >>> >>> >>> I thought that Arbitrary Branching (now referred to as Stream Branching) was initially developed for Modularity only. >>> >>> Were there any plans to use it for standalone packages as well? >> >> >> Thank you for bringing this up... I re-read the Wiki including the Factory2 link and I'm still confused. I like the idea at a high level but I still don't understand how to use it. >> >> One example is that I maintain the package OpenImageIO which has a very disciplined upstream that's careful about not making API/ABI breaking changes within a minor release. I would like to get branches for each minor release that's currently supported, 1.8 for rawhide through F28, 1.8 for F27 and 1.5 for EPEL. >> >> Like I said, at a high level it makes since, but I still don't understand exactly how to do it or if the process/tools are mature enough to actually use yet. > > > The original idea was to use it for modules [1]. You would reference the branches in your module definition [2]. > There's no particular reason it couldn't be used for regular packages. The only reason it's not done is because of convention. It's certainly workable, but as fedpkg doesn't yet support that workflow, it's a bit more manual. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ 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
