Re: channels
| From: | Clay Loveless | Date: | Mon, 22 Aug 2005 17:00:33 +0000 |
| Subject: | Re: channels | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-39482@lists.php.net to get a copy of this message | ||
Joe Stump <joe@joestump.net> wrote:
> My package depends on pearified.com's Smarty template package.
> This isn't the issue I have though, the issue I have is that
> pearified's channel installs everything into "Pearified/".
> I would think Smarty should go into HTML/Template/Smarty or
> something like that.
Hi Joe,
I understand the confusion, and thought I'd address what I can related to
it.
I know that Greg has specifically omitted any requirements for channel
packages to be installed in any particular way, since install locations
within php_dir is a political/social issue, not a technical one.
I have split feelings on the subject myself. One the one hand, I absolutely
agree with you, and feel like a big melting pot in the PEAR php_dir is fine,
and makes things less confusing for the users of channels.
On the other hand, I feel like it's helpful to keep the packages I
distribute inside /Pearified, since it means that there will (possibly) be
less confusion on where the package came from.
I believe it also allows someone else to release a Smarty package on another
channel if they so choose, without worrying about whether their version
steps on my version. (I haven't double-checked the source on this, so Greg
correct me if I'm misunderstanding this.)
In fact, this will happen soon -- I'm talking with the Smarty guys to get a
smarty.pearified.com channel together, which will make the /Pearified/Smarty
installation obsolete. By having the channel sub-directories, you will be
aware that you're using a package from another channel, since you'll need to
explicitly change you inclusion of that library.
As I said, I have mixed feelings on this, but ultimately chose to create a
/Pearified sandbox where I could choose my own set of directory naming
rules. I don't plan anything radical, but living within /Pearified gives me
flexibility to rearrange my naming convention AND be immune from any
higher-level PEAR naming scheme changes.
I'm interested in what others have to say on the subject!
-Clay
--
Killersoft.com