In article <[EMAIL PROTECTED]>,
Eloy A. Paris <[EMAIL PROTECTED]> wrote:
>The problem is that upstream ncpfs-2.0.x and ncpfs-2.1.x are different
>packages and I don't know how to create a binary package (a .deb) from two
>different source packages.
Ah, that's easy. Just look at how I did it with NIS and how Peter Tobias
does it with the network packages:
ncpfs-2.1.2/debian/
ncpfs-2.0.x/
ncpfs-2.1.x/
Just include the 2 packages into one source package. You need to be
careful with the .orig directory though (keep everything in sync).
>Also, packages ncpfs and ncpfsx have lots of
>binaries, not just the ncpmount and ncpumount binaries, so this will add
>more complexity to these stub scripts.
Just use one stub script, link all the others to it:
#! /bin/sh
kver=`uname -r`
bin=`basename $0`
exec /usr/lib/ncpfs/${kver%.*}/$bin "$@"
That will execute /usr/lib/ncpfs/xxx/binary where xxx is 2.0, 2.1 or 2.2
(.. or 3.0, etc). Note the Posix ${kver%.*} expression to strip the minor
revision number.
That's supposing the names and basic functionality of the 2.0 and 2.1
series are the same, ofcourse.
HTH
Mike.
--
Miquel van Smoorenburg | The dyslexic, agnostic, insomniac lay in his bed
[EMAIL PROTECTED] | awake all night wondering if there is a doG
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
