Re: Packing a C# project.

2008/6/11 Isak Savo <[email protected]>:

> On Wed, Jun 11, 2008 at 4:11 PM, Neil Munro <[email protected]> wrote:
> >
> > 2008/6/11 Isak Savo <[email protected]>:
> >>
> >> On Wed, Jun 11, 2008 at 2:22 PM, Neil Munro <[email protected]>
> wrote:
> >> > My application is eventually going to be a root app, it's a software
> >> > update
> >> > tool which is why I assumed the user WOULD have write access. But if
> the
> >> > file is not in the share directory and I create it in /home/whatever
> it
> >> > makes the checks for the file in share pointless, I'm confused. :s
> >>
> >> Yes! Unless you have some sort of "default" whitelist file you wish to
> >> open first. Then it should be in datadir.
> >>
> >> Point is - never expect datadir to be writable. It doesn't matter if
> >> you are root, datadir can be on a filesystem that is read-only (some
> >> people like to have it like that) and then not even root can write to
> >> it.
> >
> > So basically move all config files into /home now?
>
> Yeah. But just a note here: your *installation* should not put
> configuration stuff in /home, these config files should be put there
> by the program, when the user first runs it.


I've not even got an installer written yet, it was all going to be warp.
Figure autopackage would be a distribution neutral installer.


>
>
> I imagine in your situation, you'd put some default configuration
> files (like a default whitelist etc.) in
> $prefix/share/warp/whitelist.txt, allow the user to configure it
> (add/remove) and store those settings in
> $home/.config/warp/whitelist.txt


No default as such, user tells warp if they want a security policy if so
warp creates it, if not doesn't so I guess checking for things in ~ is now
what i need to do.


>
>
> I don't know if you plan to support user configuration of whitelist,
> or if you have a default whitelist, but hopefully you get my point.


Totally user configurable. It does not exist by default yet. Will do
eventually.


>
>
> > With the exception of
> > packages which should go in (for example) /var/warp/pkg-cache (bit like
> > apt). I had been thinking about moving packages into their own directory
> and
> > was wondering about using var, so that kinda confirms it's ok to do, so
> > thanks for that too. :)
>
> Yeah. System admins typically setup /var to be on a fast disk, and
> expect data to change frequently and thus adjust file system settings
> accordingly.
>
> -Isak
>
> >> Yes! They are (from what I understand of Warp) to be considered
> >> configuration files.
> >
> > I have feeds.txt, whitelist.txt, blacklist.txt update.xml and downloaded
> > package files, I think that's about it, so to re-iterate downloaded
> packages
> > somewhere logical in /var everything else in ~/.config/warp/bin or share
> or
> > whatever?
>
> just ~/.config/warp for (user created/modified) configuration. You can
> create subdirectories there if you want, but often its not needed. I
> suggest you take a look at what other programs do. It's the easiest
> way to figure out how it all works :)


So with all my files now in ~/.config/warp what do I do about the
Path.Combine( BinReloc.DataDir, <somefile> ) ? If these are per-user config
files then do I still use the mentioned code?


>
>
> -Isak
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
> For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]
>
>