Re: [Kolab-devel] PHP composer and packaging
Hans de Raad <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Organization | DevHdR |
| Message-ID | <[email protected]> |
I am not sure if there is an issue with application/projectlevel libraries (composer) instead of system-wide libraries in the regulatory compliance area. Usually this compliance is validated on a functional level, and as long as the functions output is reproducable in a traceable manner, this shouldnt be an issue. The fact that composer enhances autoloading is also a nice-to-have feature, which ofcourse can cause risk of "hidden" dependencies, although, these dependencies are easily mapped with other tools, or an alternative might be to actually use composer to manage the classmaps altogether. Best regards, Hans de Raad -- DevHdR Onderdeel van HaLeNaS v.o.f. Van Sevenbergestraat 49 2274PK Voorburg Tel +31 6 83578847 www.hcderaad.nl On Friday, February 07, 2014 12:00:03 PM [email protected] wrote: > Packagers, distributors and regulatory compliance usually require one > system-wide version of a particular library or capability, however.