Le mercredi 13 août 2008 à 20:06 +1000, Sven Dowideit a écrit :
> Nico,
> 
> /var/run - I'll keep that in mind for post lenny - I was really hoping
> that debian had a place for this sort of session data, but didn't manage
> to get there - thanks :)
> 

Maybe there is a web apps policy to be determined here (unless it exists
alread ?)

For instance, when considering recent issues with session files in
phpgroupware, I noticed that with php5, by default sessions may be saved
in /var/lib/php5/. But as we needed some kind of admin management of
sessions of users (like killing them) it led us to have them (back)
into /var/lib/phpgroupware/sessions/. I guess I've asked for some policy
or guidelines but got no answer.

> I'm hoping for the next release that I can move everything into
> /var/twiki (rather than scattered around the fs, including pollution the
> perl lib dirs) so that TWiki people stop being totally confused by the
> setup :/
> 

Hmmm... It seems to me it wouldn't be a good idea. See
http://www.debian.org/doc/debian-policy/ch-opersys.html#s-fhs and
http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html for
reference.

I guess code should be in /usr/ and not in /var/ right ?

I guess that current dir layout is mostly good, as there are proper
symlinks in /var/lib/twiki (bin, lib, data, pub, etc.). Once you're
looking for something starting from /var/lib/twiki, you should find it
(for TWiki folks).

Still, that /usr/share/perl5/TWiki* may not be desirable, yes. Bt I'm
pretty sure the configuration allows some curstomization of the perl
path. Still I don't know which path would be best. Maybe something
like /usr/lib/twiki/ ?

Why change something that works ? ;)

My 2 cents.

Best regards,
-- 
Olivier BERGER <[EMAIL PROTECTED]>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 1024D/6B829EEC
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to