[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#391246: general: Buildds should consider changing $HOME

On Thu, Oct 05, 2006 at 07:09:21PM +0200, Frank Küster wrote:
> 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:

Good that it's not a bug against a buildd package, since there it should
be tagged 'wontfix'.

> Steve Langasek <vorlon@debian.org> 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.

Even more alternatively, these tools should not fail horribly when
writing to directories in $HOME seems impossible for some reason. That
falls under 'standard good programming practices'.

<Lo-lan-do> Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22

Reply to: