#802: Status on Arch Linux | Splitting into Library and Application
-----------------------------+----------------------------------------------
Reporter: Xavion | Owner: lennart
Type: enhancement | Status: closed
Milestone: | Component: build-system
Resolution: distrospecific | Keywords:
-----------------------------+----------------------------------------------
Comment(by coling):
Lennart has already said that if the patch is clean he will likely apply
it.
That said, as a packager myself, I find it absolutely astounding that the
Arch build system requires that you build and install a given source
multiple times in order to package it. Every other distro I know of splits
the PA package into separate binary packages, but they only need to build
it once and the definition of which files go to which binary package is
left up to the packager to specify, not the upstream project.
To me, this requirement by the Arch build system is in no way indicative
of a "relatively advanced" package management system - it's totally
backwards :s A source tarball should be built once, and once only when
creating binary packages.
If you do just built it once then run the "make install-xxx" multiple
times with different values of xxx, then this is slightly more sensible
but pushing your Arch specific policy into upstream packages seems rather
narrow minded anyway. I know, for example, that the library packaging
policy is different in Mandriva than it is in RedHat and I know that
Ubuntu do things differently still.
This kind of split should definitely be left to the packaging system IMO.
That's my €0.02
--
Ticket URL: <http://pulseaudio.org/ticket/802#comment:8>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
_______________________________________________
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
