Re: File Naming Conventions

> > Just have a look: > > > > Net_Ident/examples/example.php > > Net_Url/docs/example.php > > Net_UserAgent/tests/example.php > > > > once installed, the directory structure would be: > > > > Net > > +-docs/example.php > > +-examples/example.php > > +-tests/example.php > > Please correct me if I'm wrong, but I think the directory structure > once installed is given by the roles of the files. > Using your example, if you declare the role of Net_Url/docs/example. > php as > "doc" (in package.xml) it will be installed as docs/Net_Url/example. > php, not Net/docs/example.php. > I'm not completly sure about this, so if someone who has actually > worked with > the roles of files could confirm or correct this, it would be greatly > appreciated. Oh, well... I just tried installing some via "$pear install" and yes, you're right. But the problem still remains for packages who don't specify any basedir: for those, docs are copied in "docs/", not in "docs/Package_Name/". Hence a stronger file naming convention may still be needed. Tnx for your comments, though! Regards, Lorenzo --- [Quipo ISP - Questa E-mail e' stata controllata dal programma Declude Virus] [Quipo ISP - This E-mail was scanned for viruses by Declude Virus]