[dev] Moving towards packages and Horde 3

[Chuck Hagenbuch]

Quoting Jon Parise <jon at horde.org>:

> > - In tarball distributions, HORDE_LIBS will be modified to point to
> > horde/lib/ (*with* the trailing slash), to use the tarball distributed
> > libraries.
>
> Is this our tarball distribution (as in, not a PEAR package tarball)?

This would be with tarballs of Horde for non-pear use (i.e., not using the pear
package manager to install the libs or eventuall the apps).

> That sounds good.  It might be nice to allow HORDE_LIBS to be set via
> an environmental variable, as well.

Yeah, I wasn't sure on the security implications/etc. of this. If people think
it's a good idea, I'll definitely add it to core.php (and probably to app
base.php files for the HORDE_BASE definition).

> The PEAR installer now has the capability to perform automake-style
> @token@ expansion in source files.  It would be trivial to get a
> package.xml file to expand @HORDE_LIBS@ to the appropriate path at
> install-time.

Neat, but the assumption was going to be that we'd set HORDE_LIBS to '' (empty)
for installs using PEAR, so they looked in the standard PEAR include path.
Other values would be for when you weren't installing with PEAR, so...

> > - Most of the content of horde/libs (except for core.php, version.php,
> > base.php, and api.php, possibly a few more) will be moved (cvs repo copied)
> > into a new module called 'framework'.
>
> Please elaborate.  Will 'framework' be a top-level module in the CVS
> sense?

Yes, like the 'pear' module in PHP CVS. Basically, it doesn't make sense to
continue to develop our packaged libraries inside horde/lib/, if we really want
to go that way.

> > - Tarball distributions will have all of the classes in the frameworks
> > module (and, possibly, all PEAR classes that we rely on) bundled into
> > horde/lib.
>
> You mean tarball distributions of Horde, yes (not our applications)?

Correct.

> It would be nice to document the new organization scheme on the web
> site once it's adopted.  That will make it conceptually easier for
> users to understand the system's layout.

Definitely. There's a lot that that can be said for, unfortunately...

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
Born right the first time.