Try unpacking the package, tarring up the result, and moving it to the
slackware system that way. If it doesn't work, you might have to
run autoconfig and build it from source under slackware.
Be sure the /var/lib/dpkg directory gets bootstrapped with something
sensible.
Thanks
On Thu, 16 Oct 1997, Bruce Perens wrote:
Try unpacking the package, tarring up the result, and moving it to the
slackware system that way. If it doesn't work, you might have to
run autoconfig and build it from source under slackware.
Be sure the /var/lib/dpkg directory gets bootstrapped
Dale Scheetz [EMAIL PROTECTED] writes:
Isn't there a non-debian tarball of dpkg somewhere?
[...] Debian/project/experimental ls -l dpkg*nondebbin*
-r--r--r-- 1 adminroot 555827 Oct 8 17:17
dpkg_1.4.0.19_alpha.nondebbin.tar.gz
-r--r--r-- 1 adminroot 459539 Jul 21 23:48
I've just been given the goahead to take over a project, in which there
are linux boxes being used about the state as mail servers and mail
monitors.
Currently, it all works, but is a set of kluges running slackware.
Ultimately, the machines will be switched over to debian (or possibly
redhat,
4 matches
Mail list logo
