Re: Backports - Best practise (or something similar)
Sex, 2006-06-02 às 16:28 +0200, Frank Küster escreveu:
> Daniel Baumann <firstname.lastname@example.org> wrote:
> > rec. 5 means basically, that you should *not* compile every program e.g.
> > against xorg, or against kde from bpo: in this case, every user of that
> > backport would also be forced to install xorg/kde/$whatever at the same
> > time (same for every unneeded dependency upgrade).
> That's a reasonable goal (as long as the package is *also* installable
> with xorg from backports.org; if that is not the case, I'm not sure what
> to prefer).
The objective is to have packages from testing instalable on sarge
directly, not in a stable/testing environment. So, if you can build that
package against everything in stable, do it. If not, do it with the less
dependencies possible, so that the stable environment is changed to the
minimum and have real stable and tested base.
> >> I would rather suggest to adjust build-depends (for example, if a
> >> package in etch has
> > ack, that is what i do too; where do you see any conflict with what i
> > said before?
> Hm, I would like to avoid a situation where I need to keep separate
> build environments up-to-date, one for each source package that I
> regularly backport, with only the specifically needed backports manually
> installed, otherwise no backports.org in the sources.list (or pinned
> down so that it won't be used). I'd rather have one backports.org
> tarball which I use with pbuilder for all builds targetted at
you can use some virtual system to test and compile.
> In an ideal case, it would install build-dependencies from sarge, unless
> a versioned Build-Depends requires a version from backports.org - then
> it would take that one. I fear this isn't possible with pinning
> currently, is it?
you can do prefer stable branch, and pine sarge-backports bellow. you
can install build-depends from sarge only if sarge has all the requested
build-depends, or from sarge-backports, if sarge has not. Apt can do
this automatically (or almost).
> With multiple tarballs, the setup gets very complicated, I'll encounter
> build failures and maybe even unusable packages.
> Regards, Frank