On Thu, Oct 03, 2002 at 10:53:19PM +0200, Jonas Meurer wrote: > On 03/10/2002 Steve Langasek wrote: > > > > It mandates an unnecessary standard for resolving namespace conflicts, > > > > and it is incompatible with upstream naming conventions in the PEAR > > > > repository (where PEAR is increasingly equivalent to CPAN). > > > > > > Then /usr/share/php/inc/<packagename> could be a solution? > > > > No, that would be the same proposal as above, with an extra directory > > needlessly added to the path. > But it's sure that there are filename conflicts. I saw db_connect.inc > thousands of times. And others also. Also, there are often subdirs: > general.inc > db/connect.inc > db/sync.inc > layout/head.inc > layout/body.inc > layout/footer.inc > Or some other stupid examples. It's terrible to package such software > then. And also for these cases, there are nearly always name conflicts. Then on a case-by-case basis, such files should be moved into subdirectories of /usr/share/php. But a blanket statement that "PHP package include files should go in /usr/share/php/<packagename>/" is wrong, because php4-pear includes belong in /usr/share/php/, not in /usr/share/php/php4-pear; php4-pear-log includes belong in /usr/share/php/, not in /usr/share/php/php4-pear-log; and so on. It is important to resolve namespace conflicts between packages that provide general-purpose include files, but this needs to be done on a case-by-case basis, as happens when all such package conflicts occur. Steve Langasek postmodern programmer
Attachment:
pgpiNQNByy08a.pgp
Description: PGP signature