Re: Building debs from CVS
-----BEGIN PGP SIGNED MESSAGE-----
On Montag, 23. Dezember 2002 02:11, Michael Schuerig wrote:
> On Sunday 22 December 2002 21:40, Ralf Nolden wrote:
> > On Sonntag, 22. Dezember 2002 18:41, Michael Schuerig wrote:
> > > So, is it possible, only for the purpose of building, to install
> > > packages in some non-standard location where they can be (directed
> > > to be) found when building dependend packages?
> > Set up a system with debootstrap and chroot into it for building. Do
> > installing there when needed for building packages. Basically it
> > comes down to the following order:
> > 1. qt-copy
> > 2. arts
> > 3. kdelibs
> Thanks, that seems to work. Almost: kdelibs has a build-dependency on
> arts-dev that doesn't seem to exist. Have overriden it and'll see if it
I have the following packaging error in kdebase now (HEAD):
debian/kdebase-bin/usr/bin/kdesud: error while loading shared libraries:
libfakeroot.so.0: cannot open shared object file: No such file or directory
dpkg-shlibdeps: failure: ldd on `debian/kdebase-bin/usr/bin/kdesud' gave error
exit status 1
dh_shlibdeps: command returned error code 2816
on woody. libfakeroot.so is in
/usr/lib/libfakeroot/libfakeroot.so....hmm...never had this kind of error
> I have never before used chroot. Are there any docs that explains how to
> use it sensibly? What are the good practices of chroot-ing? E.g., in
> <buildroot>/var/cache/apt/archives I have created hard links to the
> debs in /var/cache/apt/archives, to avoid having to download loads of
> packages. Is this sound?
I would only rely on the chroot system and not use the cache. But you can of
course use it I guess.
> Michael Schuerig If at first you don't succeed...
> mailto:firstname.lastname@example.org try, try again.
> http://www.schuerig.de/michael/ --Jerome Morrow, "Gattaca"
We're not a company, we just produce better code at less costs.
The K Desktop Environment The KDevelop Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----