On Fri, Sep 12, 2003 at 11:19:35AM +0200, Alex Polite wrote:
> Package pinning is driving my crazy. Every now and then I just have to
> have something that is only available in testing or unstable. My
> favorite option is to download the source, compile it myself and
> install in /usr/local but eve
On Fri, Sep 12, 2003 at 10:35:35AM +0100, Colin Watson wrote:
> On Fri, Sep 12, 2003 at 11:19:35AM +0200, Alex Polite wrote:
> > Package pinning is driving my crazy. Every now and then I just have to
> > have something that is only available in testing or unstable. My
> > favorite option is to down
On Fri, Sep 12, 2003 at 11:19:35AM +0200, Alex Polite wrote:
> Package pinning is driving my crazy. Every now and then I just have to
> have something that is only available in testing or unstable. My
> favorite option is to download the source, compile it myself and
> install in /usr/local but eve
On Fri, Sep 12, 2003 at 11:28:57AM +0200, Albert Dengg wrote:
> ...
> > I want to install stable, testing and unstable under separate
> > directories. All stable packs, configuration files etc goes under
> > /stable, testing packs goes under /testing and so on.
> ...
> well, here is a guide to set
...
> I want to install stable, testing and unstable under separate
> directories. All stable packs, configuration files etc goes under
> /stable, testing packs goes under /testing and so on.
...
well, here is a guide to set up debian in a chroot enviroment
http://www.debian.org/doc/manuals/ref
Package pinning is driving my crazy. Every now and then I just have to
have something that is only available in testing or unstable. My
favorite option is to download the source, compile it myself and
install in /usr/local but every now and then it's a big thing like
evolution which has a gazillion
6 matches
Mail list logo
