[haiku-development] Re: Haiku, Inc. in Contempt of Its Community

  • From: Adrien Destugues <pulkomandy@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 18 Feb 2015 09:32:49 +0100

On Wed, Feb 18, 2015 at 09:14:53AM +0100, Stephan Aßmus wrote:
> Hi,
> 
> Am 18.02.2015 um 08:08 schrieb Adrien Destugues:
> >I now have a question: is there really an use for home/config being
> >packaged? From my personal experience I have found that it is more a
> >source of confusion, for example when I have an old package installed
> >there and keep wondering why the fixes I try to install in system don't
> >seem to work. I didn't end up using it much, and put most of my packages
> >in system. The rollback from the boot menu is a good enough safety
> >system, making sure I can get back to an older state of my install if
> >things go wrong.
> >
> >So, would there be a problem in completely removing package support from
> >home/config? Are there people making use of it, and what are the use
> >cases?
> 
> Yes, the problem is that it would remove the feature of being able to
> install packages for the user only. The user may not have enough rights to
> modify the system globally. Or it may just be more appropriate to install
> some software only for one user. So please don't remove this feature.

Ok, there is a need for an user-specific "config/packages" directory,
but is there a need for a completely separate package mount point in
config? Or could the user packages be visible in /system for that user?

This way an user could "override" parts of the system with its own
packages. Would that work?

-- 
Adrien.

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 02-2015