I'll have a closer look at copr's features and its usability for building
modules soon. There's a taiga card especially for this:
http://taiga.fedorainfracloud.org/project/modularity/us/554
> And very soon it will allow defining the package set in buildchroot completely
Do you have an estimate
Dne 20.6.2016 v 15:14 Karsten Hopp napsal(a):
>
> Copy doesn't allow multiple builds with the same N-V-R either according to
> this:
> https://fedorahosted.org/copr/wiki/UserDocs#WhathappenswhenItrytobuildapackagewiththesameversionnumber
Yes. But you can have the same NEVRA in different project
On Mon, Jun 20, 2016 at 02:18:59PM +0200, Karsten Hopp wrote:
> The current idea is to use the dist tag for this and let privileged users or
> koji itself (based on some rules) overwrite the %dist tag for builds of
> module components. This lets us automate those builds fairly easily.
Obviously +1
Am 20.06.2016 um 14:48 schrieb Miroslav Suchý:
Dne 20.6.2016 v 14:18 Karsten Hopp napsal(a):
Does anyone have any other ideas for this problem ?
Rebuild it in Copr?
>
Copy doesn't allow multiple builds with the same N-V-R either according
to this:
https://fedorahosted.org/copr/wiki/UserDo
Dne 20.6.2016 v 14:18 Karsten Hopp napsal(a):
> Does anyone have any other ideas for this problem ?
Rebuild it in Copr?
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/
Hi all,
One month ago Petr Šabata posted a module build proposal here on this
list. [1]
I'd like to gather some ideas about the very first of his key points as
it poses some problems with our current buildsystem:
> - building a module means building the components it contains and
> composing
