[systemd-devel] setting up to allow separate udev and systemd builds

[William Hubbs]

On Wed, Jun 20, 2012 at 09:40:39PM +0200, Robert Schwebel wrote:
> Currently, the workflow would be like this:
> 
> 1)  build other components
> 2a) build prerequisites necessary for systemd, which are otherwhise
>     unneeded; this needs to be installed into the local sysroot in
>     order to let systemd pick up the prerequisites
> 2b) build systemd+udev
> 2c) somehow remove the "wrong" components from sysroot again, as
>     all the rest of the system is not allowed to see them (otherwhise
>     their configure scripts would assume the features to be there)
> 2d) install only udev
> 3)  move on
> 
> Instead of:
> 
> 1) build other components
> 2) configure with just the right switches, make
> 3) move on
> 
> In ptxdist, we have 700+ packages which don't need this kind of special
> handling (especially 2c will really be a pain). And all this because of
> something which can be solved in configure.ac.
> 
> Note: This discussion shouldn't be about if source distributions are a
> valid use case. Fact is that there are source distributions and people
> have their reasons to use them. And all source distributions have this
> issue. We should avoid that everyone implements his own uggly
> workaround.

Agreed. As shown in this thread, there are definitely enough use cases
out there for building stand-alone udev that this should be handled
upstream so that everyone doesn't have to invent a workaround.

Like I've said multiple times on this thread, I don't care whether or
not *my* patches get used, but it would be greatly appreciated if there
was a way to build udev standalone.

Thanks for your consideration,

William

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20120620/9252ccf2/attachment.pgp>