Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95842 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12945 invoked from network); 9 Sep 2016 10:48:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Sep 2016 10:48:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.51 mail-wm0-f51.google.com Received: from [74.125.82.51] ([74.125.82.51:35165] helo=mail-wm0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E7/62-61313-99392D75 for ; Fri, 09 Sep 2016 06:48:58 -0400 Received: by mail-wm0-f51.google.com with SMTP id w12so24448581wmf.0 for ; Fri, 09 Sep 2016 03:48:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:from:date:to:message-id; bh=RF3JozOZO21XgwPrUm0XljCLrd+W/CibuZGQ0pJmUp8=; b=k0SLtgojF6ABoIAcc0lpy/OS1lykQvWbWP6lM6nk7FWXTrV++y7QuxTnOpjHLivOIU whHcUUhmnveiHXz9IRORdSPPkCQ2LbzZaoJYhqoeCmZJDrOdWS6mT5kMO6BMrPFhT3v3 8ok6OAZQelr2P/2+y4jrVPpzmQmtkdVD9g806cJjCqBd9Wv2QsViy4xqkp5YXiUiPfgm yFkIHXCcR6IEpEb8QUTBwDfJPRc9ilZ8SlIaafszmHunYNjPx8o+QXIwlblMbqFSKQlN wn3Vf1HZbPEjvYpEEkX6DGJCb5IhK5Z0ukHiz1W52fJDmkMzgxd9Nvwe1DzFAD3OCP/x kLHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:from:date:to:message-id; bh=RF3JozOZO21XgwPrUm0XljCLrd+W/CibuZGQ0pJmUp8=; b=O502fum53XSZFDBBzAL362t9JCI/T9bHIcG9K+s4CVLorNoOhpsaDS1xk0UFUPXjRu mXn8BiV4jzZloEb3sBg+bkdDexvcc71eMOxEGL/O5vodVJrw6EOTfB/PUYleJKXM/dJ8 k/I4ZpzZNY4hp0vcIz7BFUM7/VkBsL3kSVbqerzolsHwPmbyXoxOAE9l7CRI5x4M9Ven PLttsdoQEBIsvI9yWvOVlDIH2WceW5DEUytjrva8HgySnZyyhm0egENJ2pLwZyBey+6e UZxdBf2VZq5nMjrfmris3VoO6bKr+Jwudj6BKDkwK6FwEreKqwjzVEMd/e3qS7t+BrVX a0vQ== X-Gm-Message-State: AE9vXwObSLJwTNEYmIJAmrHeUfSefoDHiN4U/6uU+3yN8WjAu5m6BQObL7zoRnAIQLL1Ag== X-Received: by 10.28.214.82 with SMTP id n79mr2385870wmg.105.1473418134140; Fri, 09 Sep 2016 03:48:54 -0700 (PDT) Received: from [10.7.12.9] (188.29.164.61.threembb.co.uk. [188.29.164.61]) by smtp.gmail.com with ESMTPSA id z17sm2716218wmz.23.2016.09.09.03.48.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Sep 2016 03:48:52 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: <616bb9ff-bcd1-fd70-b251-05b280b5003e@lsces.co.uk> References: <616bb9ff-bcd1-fd70-b251-05b280b5003e@lsces.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Date: Fri, 09 Sep 2016 11:48:47 +0100 To: "internals@lists.php.net" Message-ID: <5A7D91E4-368A-4D22-8116-286697CB5947@gmail.com> Subject: Re: [PHP-DEV] Modern practices ... From: rowan.collins@gmail.com (Rowan Collins) On 9 September 2016 09:39:07 BST, Lester Caine wrote: >Back to PEAR ... what happens if I simply install a copy of composer >centrally and rename it 'PEAR'. composer.phar simply gets installed >centrally and any new tech has access without having to install their >own copy. This is more or less how I've always used it: we don't call it "pear", but composer is placed in /usr/bin so it can be run the same way as any system command. It can be upgraded by anyone with sudo rights by running "sudo composer self-update". This makes sense to me, as that's where you'd put, say, a C compiler. Others put a local copy in with their source code, so that they can easily build the code on different boxes which might not have a copy. The important thing with composer is not where you put the tool you use to build things, but where you put the things you've built. It's similar to distributing DLLs for a Windows application: do you assume / ensure that the libraries and versions you've built against exist in the system directory (the global install that PEAR defaults to) or do you consider them part of your application, versioned and deployed as part of it (the local install that Composer defaults to). So it's not really about "play areas" or safety, it's just a philosophical and practical question of which approach is "best". Regards, -- Rowan Collins [IMSoP]