On Sat, Apr 21, 2007 at 09:20:23AM -0700, John Stamp wrote:
> Franz and I agree that replacement is the better option. The newest
> lastfm client should remain "lastfm".
>
> How do I proceed? If I were starting a new package, I'd retitle
> #413271 to ITP etc., but that doesn't seem right in
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> The slight dilemma is whether /var/cache or /var/spool would be a
> better choice. I'm leaning towards spool, as they tend to be big, and
> it would really be better not to erase them.
Well, if you ask me, I think /var/cache doesn't look that bad for t
> That's not a problem. The initial password is an empty file. Since
> it has a different owner and non-standard permissions it's a bit of
> a headache to create and remove properly in post{inst,rm}, but no
> big deal.
Just to be clear, there should be no non-conffile configuration file
shipped in
Florent Rougon wrote:
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
After your explanation, the only thing I still have doubts over is
whether the files should not go into /var/cache instead.
Erm, which files?
During the process files are encrypted. Their key is stored under
/var/lib/name,
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> After your explanation, the only thing I still have doubts over is
> whether the files should not go into /var/cache instead.
Erm, which files?
--
Florent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Florent Rougon wrote:
In case Justin's mail didn't answer all your questions...
It did.
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
Well, you would need a helper program to actually change it, as the
password is encrypted. Otherwise, yes it's a configuration file.
Well, the line is a bit
In case Justin's mail didn't answer all your questions...
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> Well, you would need a helper program to actually change it, as the
> password is encrypted. Otherwise, yes it's a configuration file.
Well, the line is a bit blurry here, I admit. Note that pa
Justin Pryzby wrote:
If you want a non-conffile configuration file, then you must not
provide the file in the package. Instead, create the file at install
time (not compile time) with the maintainer scripts (postinst
usually). If its a complicated file, store a template in
/usr/share/pkgnamehere/
If you want a non-conffile configuration file, then you must not
provide the file in the package. Instead, create the file at install
time (not compile time) with the maintainer scripts (postinst
usually). If its a complicated file, store a template in
/usr/share/pkgnamehere/...
Justin
On Sun, A
Florent Rougon wrote:
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
two questions:
1. My package has a password file. Where is the best place to store it?
/etc/name/password? /var/lib/name/password?
If the password file is a system configuration file (i.e., a file that
can be customized by the
Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> two questions:
> 1. My package has a password file. Where is the best place to store it?
> /etc/name/password? /var/lib/name/password?
If the password file is a system configuration file (i.e., a file that
can be customized by the admin to modify the
11 matches
Mail list logo
