Package requiring a customised version of another package
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have an application I'd like to package --- plasticfs. Unfortunately, due to
glibc weirdnesses, it needs a copy of glibc built using custom (non-standard)
options. Is this doable, or is it likely to be a lost cause?
Note: it doesn't need the customised version to be *installed* --- all it
needs is the .so somewhere private where it can find it.
I suppose the worst-case scenario is where I have to ship a copy of the glibc
source along with the plasticfs source and build it there... which is pretty
horrible. Not the least of which is trying to keep the various version in
sync. Of course, my build process *could* just do 'apt-get source glibc' and
patch the result...
Is there a smarter way of doing things?
- --
┌── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ─── http://www.cowlark.com ───────────────────
│
│ "There does not now, nor will there ever, exist a programming language in
│ which it is the least bit hard to write bad programs." --- Flon's Axiom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGzeaCf9E0noFvlzgRAq4/AKCZ7Vl1HXSN2pPXvGNzY1qzLPm/OgCfXaI0
z7KEvCzTsEakF9Z3QKrXp1A=
=aw6V
-----END PGP SIGNATURE-----
Reply to: