module-assistant support for zaptel

[Jose Carlos Garcia Sogo]

--=-znEK+gi7O3BIZO2/OwL/
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

El dom, 27-03-2005 a las 23:06 +0200, Tzafrir Cohen escribi=C3=B3:
> [ This post still does not refer to the issues rased by Eduard Bloch]
>=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 work with
> > automated builds. It requires quite a lot of initial setup, and most of
> > it appears to be the job of root.=20

  Yes, for running in /usr/src you have to run m-a as root. Basically #
m-a a-i zaptel should do the trick.=20

> >=20
> > In addition, packaging the files in an internat tgz bypasses any sanity=
=20
> > check lintian and others would do to them.

  But there is no check that lintian can make to those files. Lintian
could only work in user generated zaptel-modules package. If you check
any other kernel modules package, you will see that source is also
placed in a tar.gz file.

> >=20
> > I've played with it all day long and it seems very unsuitable for
> > non-root builds. If it requires that the code module is compressed 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=
.

  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.

>=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 manually
> 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 file .

  The control file for modules is autogenerated by m-a from
control.modules.in. That allows adding kernel version number to package
name and description.

  Please, recheck m-a as it is a nice and easy tool, which will solve us
a lot of user problems.
=20
  Cheers,

--=20
Jose Carlos Garcia Sogo
   jsogo@debian.org

--=-znEK+gi7O3BIZO2/OwL/
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD4DBQBCRyeZS+BYJZB4jhERAlm5AJUZ9Xgj1CZjtJeBKd476uMYAe0xAKChoYHT
CJkMOArj4H5bQ9/XUJCDcQ==
=u9tJ
-----END PGP SIGNATURE-----

--=-znEK+gi7O3BIZO2/OwL/--