And of course, the seed is not technically required, everything could
be done with a generic
* chain build
* chain build remainer with bootstrap
* chain build bootstrapped builds normally
* chain build everything
The seed just saves days of processing build farm side
--
Nicolas Mailhot
Le mardi 16 avril 2019 à 15:39 +0100, Mat Booth a écrit :
>
> Why wouldn't this work for you? You would just rebuild the module a
> second time without the bootstrap flag set. This is fairly standard
> process for packages that buildrequire themselves and not unique to
> golang.
I may be wrong, b
On Tue, 16 Apr 2019 at 14:14, Robert-André Mauchin
wrote:
>
> On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
> >
> > Yes, there is a buildopts section in the yaml file where you can specify
> > rpm macros.
> >
> > Here is the documentation:
> >
> >
https://docs.fedoraproject.org/en-US/mo
On Tue, Apr 16, 2019 at 3:14 PM Robert-André Mauchin
wrote:
> On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
> >
> > Yes, there is a buildopts section in the yaml file where you can specify
> > rpm macros.
> >
> > Here is the documentation:
> >
> >
> https://docs.fedoraproject.org/en-US
On Tue, Apr 16, 2019 at 11:11 AM Petr Pisar wrote:
>
> On 2019-04-16, Igor Gnatenko wrote:
> > You can do something like:
> >
> > rpms:
> > foo-bootstrap:
> > name: foo
> > bar:
> > buildafter:
> > - foo-bootstrap
> > foo:
> > buildafter:
> > - bar
> >
>
> How does f
Le 2019-04-16 15:06, Robert-André Mauchin a écrit :
On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
Yes, there is a buildopts section in the yaml file where you can
specify
rpm macros.
Here is the documentation:
https://docs.fedoraproject.org/en-US/modularity/making-modules/definin
On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
>
> Yes, there is a buildopts section in the yaml file where you can specify
> rpm macros.
>
> Here is the documentation:
>
> https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modu
> les/#_build_macros_optional
>
> H
On 2019-04-16, Igor Gnatenko wrote:
> You can do something like:
>
> rpms:
> foo-bootstrap:
> name: foo
> bar:
> buildafter:
> - foo-bootstrap
> foo:
> buildafter:
> - bar
>
How does foo.spec get to know that it should enable bootstrapping in
foo-bootstrap component,
You can do something like:
rpms:
foo-bootstrap:
name: foo
bar:
buildafter:
- foo-bootstrap
foo:
buildafter:
- bar
However, MBS doesn't support that yet.
On Tue, Apr 16, 2019 at 1:35 AM Robert-André Mauchin
wrote:
> Hi,
>
> In Golang, we have a lot of cyclic depend
On Tue, 16 Apr 2019 at 00:29, Robert-André Mauchin
wrote:
>
> Hi,
>
> In Golang, we have a lot of cyclic dependencies for which we have to
bootstrap
> many packages, and then later build them unbootstrapped when all the deps
are
> in place.
> How are we supposed to handle this in Modularity? Since
10 matches
Mail list logo