module-assistant support for zaptel

[Tzafrir Cohen]

On Sun, Mar 27, 2005 at 11:37:29PM +0200, Jose Carlos Garcia Sogo wro=
te:
> El dom, 27-03-2005 a las 23:06 +0200, Tzafrir Cohen escribi=F3:
> > [ This post still does not refer to the issues rased by Eduard Bl=
och]
> >=20
> > On Sun, Mar 27, 2005 at 02:13:44AM +0200, Tzafrir Cohen wrote:
> > > After playing with m-a a bit, I still don't see it saving me wo=
rk with
> > > automated builds. It requires quite a lot of initial setup, and=
 most of
> > > it appears to be the job of root.=20
>=20
>   Yes, for running in /usr/src you have to run m-a as root. Basical=
ly #
> m-a a-i zaptel should do the trick.=20

However for multiple kernels you basically have to extract the trees.

>=20
> > >=20
> > > In addition, packaging the files in an internat tgz bypasses an=
y sanity=20
> > > check lintian and others would do to them.
>=20
>   But there is no check that lintian can make to those files. Linti=
an
> could only work in user generated zaptel-modules package. If you ch=
eck
> any other kernel modules package, you will see that source is also
> placed in a tar.gz file.

Did you notice you add -m 644 to almost every install (you actually
forgot it with some, and used plain cp). lintian won't check file mod=
es
inside a tarball.

Anyway, what about /usr/include/linux/torisa.h ? Can zaptel-source
provide it?

>=20
> > >=20
> > > I've played with it all day long and it seems very unsuitable f=
or
> > > non-root builds. If it requires that the code module is compres=
sed to a
> > > rather than kept in its own directory than it really does harm.=
 If not,
> > > I have no problem with it and it might actually turn out useful=
 one day.
>=20
>   If you want to use it as non-root you have to pass --user-dir dir=
/ to
> m-a, being dir a directory you have permissions.

Been there, done, that and read the man page. The docs of the package
leave me with a feeling that "this is fine if you want to run it as r=
oot
and mess your own /usr/src , however if you run it as user, you're on
your own".

>=20
> >=20
> > After some extra games: I couldn't make anything useful with m-a =
so I
> > reverted back to my original makefile for building the modules. I
> > changed the package so that the source will be extracted under
> > /usr/src/modules/zaptel-source and this appears to work well, but=
 I
> > never did get m-a to work.
> >=20
> > However the package still lacks a control file. I added it back m=
anually
> > and started building, but found no way to generaet a changes file=
 for
> > the generated package: dpkg-genchanges complained that the files =
list
> > was missing. This is where I left it. I attach my current rules f=
ile .
>=20
>   The control file for modules is autogenerated by m-a from
> control.modules.in. That allows adding kernel version number to pac=
kage
> name and description.
>=20
>   Please, recheck m-a as it is a nice and easy tool, which will sol=
ve us
> a lot of user problems.

I have checked, double checked and triple checked. So far, I'm very
disapointed.=20

--=20
Tzafrir Cohen     icq#16849755  +972-50-7952406
tzafrir.cohen@xorcom.com  http://www.xorcom.com