Re: Variable in Depends: ??
Russell, other interested Debians
Thanks for the detailed suggestions. Let me introduce a small cast, and
then define the more troublesome, general problem with respect to
Debian.
Mark Spieth applies the code upgrades to the open source ltmodem.o
components and has written most of the kit at
http://walbran.org/sean/linux/stodolsk/ ltmodem-5.78e.tar.gz. Therein
I've maintained the DOCs and embellished the ./ltinst a bit.
Mark uses rpm, while Chris Hebeisen & I have Debian installations.
Though we couldn't include it the current package Chris has started work
on a much more general installer, with relevance to the general problem.
Winmodems are becoming increasingly prevalent within the new PCs and
laptops. These Afflictions cannot be long ignored as both Newbies and
experienced increasing need them to get on line under Linux.
There is a LOT of Trouble Traffic on the List discuss@linmodems.org
With respect to Linux, the best of the Linux supported winmodems have
some closed source components, that are combined/compiled with open
source components and kernel-headers to generate kernel-version-matched
binary modules. Currently this includes modems with Lucent/Agere
chipsets, the Mwave in newer IBM Thinkpads, Intel/Ambient HaM, and
(expected drivers for) Motorola chipsets.
What we really need for Debian I thing, is a general installer package
which would:
1) apt-get install kernel-headers make (and dependents)
2) request separate import of the proprietary component (as now done for
the Real Player) and then
3) process its included Makefile to generate the modem drivers
4) install the drivers in the /lib/modules/
This is WAY Beyond my scripting skills/knowledge. They are more at the
level of using alien for elementary Package.deb constructions. My 1st
cut at the ltmodem installer ONLY before packing has structure:
|-- debian
| |-- control,etc
| `-- rules
`-- usr
|-- bin/ltmodem
|-- share-doc-ltmodem (5-6 Docs)
`-- src-modules
`-- ltmodem
|-- build_module
`-- ltmodem-5.78e.tar.gz
wherein bin/ltmodem is basically Chris's script component for
version/resource checking, which if OK, calls Mark's build_module, which
builds and installs ltmodem.o from ltmodem-5.78e.tar.gz. Mark (in your
time zone?) can give you an environmental variable supporting builds
from non-version matched kernel-headers.
Russell I'll tarball this up and send it to you, for anything you might
choose to contribute. There is NO PRIDE of ownership herein whatsover.
Rather, I'm much more fearfull of the general problem not being
adequately addressed. Some solution is needed for the maturing boot
disks in particular. Otherwise a lot of Debians will have to
build/maintain their full installations via some sort of an
intermediate (apt-zip style?) + Microsoft ppp.
MarvS
> Russell Coker wrote:
>
> On Sunday 25 February 2001 04:49, Marvin Stodolsky wrote:
> > Per below, I am Debianizing a modem driver package. In principle it
> > would be preferable to specify the Depends: for header-sources by
> > something like:
> > Depends: kernel-header-`uname -r`
>
> You are assuming that the version of the kernel that is being run is the same
> as the version that is being compiled for. This is bad and means multiple
> reboots if you want to compile for multiple kernels.
> "uname -r" should be replaced with the following:
> head -4 /usr/src/linux/Makefile | sed -e "s/ //g" > foo
> echo "echo \$VERSION.\$PATCHLEVEL.\$SUBLEVEL\$EXTRAVERSION" >> foo
> /bin/sh ./foo
>
> > to achieve a required version matching with the running kernel
> > Rather then the (generally incorrect) specification of a particular
> > version. Is there anyway that this can be simple implemented in the
> > initial Pre-install, or must it be left to Messages under the
> > post-Install scripts?
>
> Why not have a wrapper script that uses sed to create a debian/control file
> and then runs dpkg-buildpackage? It wouldn't work with auto-builders, but I
> doubt that there is a need to use auto-builders at ltmodem is Intel-only (and
> includes an Intel .o file that lacks source).
>
> --
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/ My home page
Reply to: