Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94962
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.214.46 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <9ccdcfcd-7a1c-42df-c893-398781e1f1d2@lsces.co.uk>
References: <CADqTB_gBFM_2yNDQemPs68Fab4Hbd8pGj38a3-HSQ+CRcnDyvA@mail.gmail.com>
 <ee6521f3-123b-83bf-5b7f-b20d0bc4b832@lsces.co.uk> <CADqTB_jTGGx=Xvq8vQab2YZoOuuyr7E6a_NWmgaYbARAJPSJ3g@mail.gmail.com>
 <9ccdcfcd-7a1c-42df-c893-398781e1f1d2@lsces.co.uk>
Date: Mon, 8 Aug 2016 22:54:02 -0700
Message-ID: <CAESVnVoCkp+ZszmigzmNt6+HLqi8pLB2Xi8a4cYM-=01x=rZqw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Function auto-loading
From: pollita@php.net (Sara Golemon)

On Mon, Aug 8, 2016 at 9:59 PM, Lester Caine <lester@lsces.co.uk> wrote:
>> That is, when I'm running the test-suite of my package, the Composer
>> project is the root folder of that package - but when the package is
>> being consumed by another project, it's installed in a sub-folder in
>> that project's "vendor" folder.
>
> So Composer IS now the rule rather than some optional extra?
>
Yes, the community has decided that for us.  Or at least, Composer is
a *significant* player in the ecosystem of PHP development.
require_once() might be fine for NiH applications, but for the
collaborative world of modern PHP, it's the defacto standard.

> It is OK
> for users who only want to load the one application, but when one is
> running a large number of different packages it's a major hindrance.
>
You'll need to back that up with some more detail.  Composer is
specifically designed to _compose_ through multiple packages and also
allows for isolation when that sort of blending doesn't make sense.
Far from a hinderance.

> I don't need to know where my Linux install has put the include files ...
> it takes care of that and then finding the pigging things again is the
> problem.
>
So, autotools and cmake and the like exist for what purpose then?
Even pkg-config, which was supposed to solve much of this problem is
incomplete, at least on GNU distributions, falls short.

> Much the same with finding the source of problems in the mess
> that composer has created!
>
[citation required]

-Sara