Package: general
Severity: wishlist

"general" is not the best package to report this to, but since there's
no "buildd" package, and I don't want it to be completely forgotten,
I'll report it here.  I'm quoting from a bugreport where we came across
this, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388399;msg=123:

Steve Langasek <[EMAIL PROTECTED]> wrote:

> On Wed, Oct 04, 2006 at 09:32:16AM +0200, Frank Küster wrote:
> 
> > However, I'd like to point out that this problem is not special to TeX.
> > Many programs create ~/.progname directories when run for the first time
> > - and these directories contain configuration options which might cause
> > trouble, since they are not updated or subject to dpkg conffile
> > questions when the package changes configuration options.  It might be a
> > good thing to require such tools to have a commandline switch or obey a
> > commandline variable that prevents this.  Alternatively, HOME could be
> > set to the temporary build directory, so that everything happens there.
> 
> Yes, that's true.  Setting $HOME to something explicitly nuked by the clean
> target might be a good general solution.  In practice, there are few tools
> that have broken buildd chroots in the manner that tex seems to have here.

Regards, Frank



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.17-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

-- 
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)

Reply via email to