[dev] Re: [cvs] commit: accounts/lib base.php agora/lib base.php ansel/lib base.php babel/lib base.php chora co.php chora/lib base.php forwards/lib base.php genie/lib base.php giapeto/lib base.php gollem/lib base.php hermes/lib base.php imp/lib base.php ingo/lib ...

Jan Schneider jan at horde.org
Fri Oct 24 03:57:00 PDT 2003


Zitat von Roman Neuhauser <neuhauser at bellavista.cz>:

> # neuhauser at bellavista.cz / 2003-10-24 12:20:11 +0200:
> > # chuck at horde.org / 2003-09-20 13:10:41 -0700:
> > > chuck       2003/09/20 13:10:41 PDT
> >
> > >   Log:
> > >   Use horde/lib/core.php in all applications. For now, I've commented
> > >   out the HORDE_LIBS-based includes in core.php and we're still using
> > >   the old HORDE_BASE . '/lib/' includes everywhere. But the
> HORDE_LIBS
> > >   constant is now available everywhere and core.php is included to
> > >   properly set up the base framework.
> >
> >     seeing the commented out lines in horde/lib/core.php:
> >
> >     require_once HORDE_LIBS . 'Horde/Horde.php';
> >
> >     Horde.php being in horde/lib, are you planning another path change?
> >
> >     I haven't found much about HORDE_LIBS in the archives; where is the
> >     code heading?
>
>     ignore the first question, I found the right post right after
>     sending the mail out, of course.
>
>     the second question still stands. what are the intentions regarding
>     especially */lib/base.php files, and generally moving from
>
>     HORDE_BASE . '/lib/Foo.php' to HORDE_LIBS . 'Horde/Foo.php' ?

Having the libraries distributed and managed as separate packages and
installable/upgradeable by the PEAR installer.

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft


More information about the dev mailing list