Building multiple version of a package from same dist-git repo

[Igor Gnatenko]

Hello,

is it possible to build packages like foo0.6 from dist-git repo with name
foo and not foo0.6?

Since in Rust ecosystem from time to time we need to build multiple
versions of a same package, it is much easier if it would be one repo with
branches 0.6, 0.7 instead of multiple separate git repos.

If not, what are the limitations?
-- 

-Igor Gnatenko

[Adam Williamson]

On Sun, 2018-09-02 at 17:51 +0200, Igor Gnatenko wrote:
>  Hello,
>  
>  is it possible to build packages like foo0.6 from dist-git repo with name
>  foo and not foo0.6?
>  
>  Since in Rust ecosystem from time to time we need to build multiple
>  versions of a same package, it is much easier if it would be one repo with
>  branches 0.6, 0.7 instead of multiple separate git repos.
>  
>  If not, what are the limitations? 
Isn't this exactly what 
https://fedoraproject.org/wiki/Changes/ArbitraryBranching was supposed
to be about? Not that I've seen many (any?) packages actually using it.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

[Adam Samalik]

On Sun, 2 Sep 2018 at 18:21, Adam Williamson <adamwill(a)fedoraproject.org&gt;
wrote:

>  On Sun, 2018-09-02 at 17:51 +0200, Igor Gnatenko wrote:
>  > Hello,
>  >
>  > is it possible to build packages like foo0.6 from dist-git repo with name
>  > foo and not foo0.6?
>  >
>  > Since in Rust ecosystem from time to time we need to build multiple
>  > versions of a same package, it is much easier if it would be one repo
>  with
>  > branches 0.6, 0.7 instead of multiple separate git repos.
>  >
>  > If not, what are the limitations?
>
>  Isn't this exactly what
>  https://fedoraproject.org/wiki/Changes/ArbitraryBranching was supposed
>  to be about? Not that I've seen many (any?) packages actually using it. 

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?


>  --
>  Adam Williamson
>  Fedora QA Community Monkey
>  IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
>  http://www.happyassassin.net
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]
>  
-- 

Adam Šamalík
---------------------------
Software Engineer
Red Hat

[Richard Shaw]

On Mon, Sep 3, 2018 at 1:32 AM Adam Samalik <asamalik(a)redhat.com&gt; 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.

Thanks,
Richard

[Richard Shaw]

On Mon, Sep 3, 2018 at 6:56 AM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:

>  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.
>  
That was supposed to be 1.7 for F27... Need more coffee.

[Adam Samalik]

On Mon, Sep 3, 2018 at 1:57 PM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:

>  On Mon, Sep 3, 2018 at 1:32 AM Adam Samalik
> <asamalik(a)redhat.com&gt; 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].

[1]
https://docs.fedoraproject.org/en-US/modularity/making-modules/adding-new...
[2]
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-m...


>  Thanks,
>  Richard
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]
>  


-- 

Adam Šamalík
---------------------------
Software Engineer
Red Hat

[Neal Gompa]

On Mon, Sep 3, 2018 at 8:02 AM Adam Samalik <asamalik(a)redhat.com&gt; wrote:
>  On Mon, Sep 3, 2018 at 1:57 PM Richard Shaw <hobbes1069(a)gmail.com&gt; wrote:
> >
> > On Mon, Sep 3, 2018 at 1:32 AM Adam Samalik <asamalik(a)redhat.com&gt; 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!

[Adam Samalik]

On Mon, Sep 3, 2018 at 3:02 PM Neal Gompa <ngompa13(a)gmail.com&gt; wrote:

>  On Mon, Sep 3, 2018 at 8:02 AM Adam Samalik
> <asamalik(a)redhat.com&gt; wrote:
>  >
>  >
>  >
>  > On Mon, Sep 3, 2018 at 1:57 PM Richard Shaw <hobbes1069(a)gmail.com&gt;
>  wrote:
>  >>
>  >> On Mon, Sep 3, 2018 at 1:32 AM Adam Samalik <asamalik(a)redhat.com&gt;
>  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.
>  
Ah, please don't take me wrong, I'm not opposing that. Just hinting why the
wiki page might look confusing.

I think I saw a way to submit a traditional RPM build from a different
branch by specifying the target manually.


>  --
>  真実はいつも一つ！/ Always, there's only one truth!
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]
>  

-- 

Adam Šamalík
---------------------------
Software Engineer
Red Hat

[Lubomír Sedlář]

Neal Gompa píše v Po 03. 09. 2018 v 09:01 -0400:
>  On Mon, Sep 3, 2018 at 8:02 AM Adam Samalik
> <asamalik(a)redhat.com&gt;
>  wrote:
>  > 
>  > 
>  > 
>  > On Mon, Sep 3, 2018 at 1:57 PM Richard Shaw <hobbes1069(a)gmail.com&gt;
>  > wrote:
>  > > 
>  > > On Mon, Sep 3, 2018 at 1:32 AM Adam Samalik <asamalik(a)redhat.com&gt;
>  > > 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. 
Well, this should be fedpkg 1.35 (in updates-testing now):

https://pagure.io/fedpkg/c/bcbb337e5076f8edad332067a64b7d4e6da279b6?branc...
Basically: create a config file in the repo and then fedpkg build
should be able to submit builds for multiple versions of Fedora.

https://docs.pagure.org/fedpkg/releases/1.35.html#submit-builds-from-stre...


>  
>  
>  -- 
>  真実はいつも一つ！/ Always, there's only one truth!
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  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/[e-mail]

[Mikolaj Izdebski]

On 09/02/2018 05:51 PM, Igor Gnatenko wrote:
>  Hello,
>  
>  is it possible to build packages like foo0.6 from dist-git repo with name
>  foo and not foo0.6?
>  
>  Since in Rust ecosystem from time to time we need to build multiple
>  versions of a same package, it is much easier if it would be one repo with
>  branches 0.6, 0.7 instead of multiple separate git repos.
>  
>  If not, what are the limitations? 
There are no technical limitations for building packages like that in
Koji, but you won't be able to tag them unless %{name} is added to
appropriate tag.

-- 
Mikolaj Izdebski
Senior Software Engineer, Red Hat
IRC: mizdebsk