Re: Gentoo package (--with-driver=any)

[Diego I. <ias...@ac...>]

some time ago, you said you will make an howto about building lirc=20
pre-compiled pakcages.=20

I want to make an rpm for lirc, with all drivers builded in separate rpms=
=2E=20
Will I need to build those rpms so they conflict each other?
How can I builld all the packages? (simple make in each subdir?)

Thanks in advance.

- diego
=E1=E9=E5=ED =F9=EC=E9=F9=E9 09 =E9=E5=EC=E9 2002, 17:45, Manuel Estrada =
Sainz =EB=FA=E1:
> On Tue, Jul 09, 2002 at 02:47:20PM +0200, Georg Sauthoff wrote:
> > Hi,
> >
> > On Tuesday 09 July 2002 00:46, Manuel Estrada Sainz wrote:
> > >  Yes, there is a reason for that, I implemented the --with-driver=3D=
any
> > >  option to make it easier to make debian packages of lirc with as m=
uch
> > >  functionality on them as posible. And in debian the kernel drivers=
 are
> > >  compiled somewhere else, not at the same time as the rest of lirc.
> >
> > Ok that makes sense (for debian).
> >
> > >  Building the right kernel module automatically doesn't make much s=
ense
> > >  then you use --with-driver=3Dany, because 'the right one' is all o=
f them
> > >  and since kernel modules are somewhat special to build I find usef=
ull
> > >  to packagers like you and me to not have them build automatically.
> >
> > Hm,  I just thought that "any" as paramter for --with-driver means: a=
ll
> > driver will be build. Now it is clear.
>
>  In lirc there are two layers of drivers, one in kernel space and one i=
n
>  userspace (lircd) --with-driver=3Dany means that as many as posible
> userspace drivers are included into lircd. So yes, to some extend it do=
es
> mean that all drivers are built, but just the userspace part.
>
> > >  Since Gentoo's packages are source packages all this may not make =
that
> > >  much sence, if you have any other cuestion, comment or suggestion
> > > about it, please go ahead.
> >
> > Thanks. A configure option like --disable-use-depmod would be usefull=
 for
> > Gentoo, too, because in Gentoo 'make install' is executed in a 'sandb=
ox'
> > so it has no write access to the real filesystem. In this case depmod=
 -a
> > can't modify /lib/modules/modules.dep and violates the 'sandbox' (dep=
mod
> > -a is executed by the ebuild later and the files are copied by emerge=
 to
> > the real fs).
> > Ok I have make a quick (perhaps dirty) patch for gentoo so no depmod =
is
> > executed by 'make install'.
> > Because I am not a real big configure scripts expert yet, I don't kno=
w if
> > it is difficult/simple to implement it?
>
>  It is quite simple, but I am not sure if that is the right way to go.
>  Having a lot of options that all packagers will use together. Maybe
>  having --enabled-sandboxed or something like that and not doing
>  anything that gets out of the instalation directory when it is used.
>
>  I will write it on my TODO file. For now, keep in mind, that if you us=
e
>  --with-driver=3Dany it will not try to run depmod on 'make install', a=
nd
>  you can just install kernel modules explicitly.
>
>
>  ranty