Paths dilema

Toshio Kuratomi a.badger at gmail.com
Mon Jun 20 20:07:11 UTC 2011


On Mon, Jun 20, 2011 at 08:39:24PM +0300, Marian Marinov wrote:
> On Monday 20 June 2011 19:37:38 Toshio Kuratomi wrote:
> > 
> > Look at the MochiKit package for one example:
> > http://pkgs.fedoraproject.org/gitweb/?p=MochiKit.git;a=tree
> > 
> > Also look at
> > http://fedoraproject.org/wiki/JavaScript_libraries_packaging_guideline_draf
> > t for some more current ideas (This is just a draft so it's not to be taken
> > as MUSTs for now, though.)
> 
> Toshio, thanks for the information. It was quire helpful. 
> 
> But now I have more questions :)
> Since currentle there isn't %{_sysconfdir}/js.d/ wouldn't it be better if i 
> create a %{_sysconfdir}/httpd/conf.d/jslibs.conf in which I define alias for my 
> library:
>   Alias /js/extjs /usr/share/extjs
> 
> And we can then add additional aliases to that file.
> 
+1

yeah, since the javascript library guidelines are still a draft, that extra
dir doesn't exist so your proposal works well.

> > 
> > > Also if it is under /var/www wolfy mentioned that it would be best if it
> > > is not web accessible, what are your toughs about that?
> > 
> > It should not be under /var/www... Use the apache.conf to set it up to be
> > served.
> 
> Do you mean that I have to have a %{_sysconfdir}/httpd/conf.d/hawk.conf (Hawk 
> is the name of my application). And in it to have aliases setup for my 
> application? If so, where should the web interface reside? Under 
> %{_datadir}/hawk ?
> 
I was talking specifically about the javascript library but yeah, /var/www
shouldn't directly be used for hawk either.  Your proposed solution sounds
good.  Take a look at:

http://fedoraproject.org/wiki/Packaging:Guidelines#Web_Applications

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/epel-devel-list/attachments/20110620/a83c6320/attachment.sig>


More information about the epel-devel-list mailing list