Le Lun 14 décembre 2009 11:28, Josephine Tannhäuser a écrit : > > 2009/12/14, Nicolas Mailhot <nicolas.mailhot@xxxxxxxxxxx>: >> The guidelines should be read as: >> >> « Bundling any other component your component depends on in the same package >> is forbidden; each component should be packaged separately in its own >> package >> for legal and maintenance reasons » > This is more a wishful thinking than a practical thing.... > The guidelines should be a system of rules without place for everyone > to interprete in it what he/she wants to see in the guidelines. I don't have the time right now but I personally would not hesitate to propose this as a formal packaging guideline if FPC feels it is not what the current guidelines intended (but did not express cleanly). Every domain I've packaged has the same recurring maintenance problems with bundled components (be it libraries, java jars, reference files), there is nothing library specific in the problems bundling causes (forking, non tracking of upstream fixes, conflicts, etc) So, you may think this is wishful thinking, but on my experience it is a very practical and pragmatic rule. Bundling helps you get new components in fast and then makes package maintenance a burden forever (years after years). -- Nicolas Mailhot -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
