[haiku-development] Re: PM Mount Points
- From: Adrien Destugues <pulkomandy@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 19 Feb 2015 21:29:50 +0100
On Thu, Feb 19, 2015 at 12:13:48PM -0800, pete.goodeve@xxxxxxxxxxxx wrote:
> Seems to me that the main use for find_directory is actually when
> you want to *write* something -- you need to put something in the
> User Settings folder, say. So getting a read-only pointer back may
> not be much help.
Both the settings and cache folders are always writable.
>
> > >
> > >
> > > It strikes me, though, that a strategic link or two could easily handle
> > > this. '~/packaged/settings'
> > > could just be a fixed link to '~/config/settings', so the user (and the
> > > package installer) would only
> > > have to think about the one folder. It might even be nice to have
> > > '~/config/packages to be a link
> > > to ~/packaged/packages, so again the user would usually not have to be
> > > concerned with the
> > > packaged tree at all.
> >
> > I would prefer the packages to stay in system and config
> > (system/packaged or config/packaged as it was suggested earlier).
> > Top-level directories such as /boot/common or ~/packages are made much
> > more visible, and they don't need to be there at the FS root or in the
> > home directory.
>
> Not quite sure what you're saying here, but I don't think we're
> disagreeing much.
It's still a minor difference of which path to use.
Current situation:
/boot/system (packages)
/boot/system/non-packaged (not packages)
~/config (packages)
~/config/non-packaged (not packages)
Your proposal is:
/boot/system or /boot/system/packages? (packages)
/boot/common (not packages)
~/packages (packages)
~/config (not packages)
And what I'd prefer in that case (I'm fine with either this or the
current one):
/boot/system (not packages)
/boot/system/packaged (packages)
~/config/packaged (packages)
~/config/ (not packages)
--
Adrien.
Other related posts:
