tags 304733 confirmed help
thanks

On Thu, 14 Apr 2005 21:11:06 -0400
"Anthony L. Awtrey" <[EMAIL PROTECTED]> wrote:

> Package: libapache2-mod-musicindex
> Version: 0.99.5.2
> Severity: wishlist
> 
> 
> I personally prefer to keep required icons and things out of the real
> web root. I moved mine to /usr/share/magicindex and added a config file
> for the mod:
> 
> /etc/apache2/mods-available/musicindex.conf
> 
> The config file contains:
> 
> Alias /musicindex/ "/usr/share/musicindex/"
> <Directory "/usr/share/musicindex/">
>   Options Indexes MultiViews
>   AllowOverride None
>   Order allow,deny
>   Allow from all
> </Directory>
> 
> If it doesn't violate some policy I'm aware of, it seems like a good
> idea to me. Thanks!

I think this is probably the good thing to do.

Yet, there are two issues I don't know how to fix at the moment:

1) find and implement a proper way to let the user add his own CSS (as it
is currently possible by dropping them into /var/www/musicindex.

To achieve that, I have to think of a best place to let the user put them
in, and add the proper hooks in the code.

2) Moving the files to /usr/share and provide a sample configuration is
trivial. Dealing with upgrades from previous versions to the new scheme is
far from being trivial, because I can't remove unconditionally
/var/www/musicindex, nor move it (if the user has symlinks they'll break
otherwise).

The best thing I can think of at the moment is install the new files in
place, and if /var/www/musicindex exists, prompt the user a message
telling him to move his files.

Considering these two issues I'm a bit clueless about right now, and the
close up of sarge release, I think I'll postpone fixing this bug to
*after* the release of sarge, unless somebody can come up with a good
patch to help me :)

Thanks for reporting anyway,

Thibaut VARENE


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

Reply via email to