On Sat, Jan 7, 2017 at 11:01 AM, Sven Kieske <[email protected]> wrote:
> On 06/01/17 18:45, Vojtech Szocs wrote: > > Today, we require `patternfly1` as both Engine RPM build dependency and > the > > Engine devel. env. dependency. > > > > To keep things simple, I'd like to propose the following approach: > > > > - create oVirt specific package, e.g. `ovirt-patternfly`, hosted at Copr, > > containing PatternFly + associated libraries (Bootstrap, jQuery) which > > are intended *specifically* for use by oVirt UI (hence the ovirt > prefix) > > > > - discontinue maintenance of `patternfly1` package at Copr > > afaik you're also requiring patternfly1 for ovirt-engine installation, > not just dev or build env? > > if that is correct and your new "ovirt-patternfly" would superseed that > I'm afraid you would violate fedora and rhel/centos package guidelines > by throwing this all together in one package? > Yeah. It's all thrown into the 'patternfly1' package currently anyway, so there's really no change here. > > I hope I understood the scope of this correct, if not, just disregard my > comment. > > -- > Mit freundlichen Grüßen / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > Königsberger Straße 6 > 32339 Espelkamp > T: +495772 293100 > F: +495772 293333 > https://www.mittwald.de > Geschäftsführer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/devel > -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer [email protected]
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
