Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95628 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22577 invoked from network); 5 Sep 2016 04:19:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Sep 2016 04:19:39 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.45 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.220.45 mail-pa0-f45.google.com Received: from [209.85.220.45] ([209.85.220.45:34023] helo=mail-pa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 22/26-45301-952FCC75 for ; Mon, 05 Sep 2016 00:19:39 -0400 Received: by mail-pa0-f45.google.com with SMTP id to9so19728472pac.1 for ; Sun, 04 Sep 2016 21:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=1IdPJfl4xUn7zx/pFdP07pzNkn98iSHVqUtgQMrH5ls=; b=l1frzIX627LtVzCcKJVFXDgqN6d7wgekp1D2aqIAhfaCHl7rxSYcWS60SRijaW0zaY 6+3OIck3f7DvgyiFLLTNFsnCramsJtzb5ThNG29kWjdh9AtFNLbelhiXqb4Sa5X3f0L+ dE0f0ADqLbc7oK3P7f24oyZugjJEJyL/8WTyAARWi8AnKoVIrd16dt/nJWryHUbqeKAh QOSc0z1mjzw8QF2+hVcTMgpr3uT/qQJwYnq1yRb7Z6qC0eg21Jm4lMeWCt6rmKisvmzU eioqOVkqmDtjV5Who+Q0NmRl1Svxf0xhDI9i8BjeGnTdoLM3X/ehYHbLwQQQq7SsabPD AiQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=1IdPJfl4xUn7zx/pFdP07pzNkn98iSHVqUtgQMrH5ls=; b=eg2W33UNU+Q8plYYZQTEeTKFgnoxXpwMFLMTJOcb5yY9ckwMSfg5qp/pTKBeV/ZSye MGWxTO1fOe+0c8DF8EjZc6m5YLGd5kCeqY/FWBZcf/ASMyToMZy813m5qk4oRAYCUy6s mFe5c+3GD60kliWaLBXg6FcWnFekAyuyYY10l7ou8ZAapBZDLBMMfSIFcV/QI9GMRGs/ TXPCOxhkJXIZyzLpIuqPqeo/OB/aBDXVV82VG1ajMu1IPdHB+U2a9ub9TKRj8oIii0+Z jnqJhwIo0lP25K+DAM995wH/BILYc4H4zKj/01YhmZcYOlYz0pkW9dJ0QCk0jmMD6RqM uaMw== X-Gm-Message-State: AE9vXwM8j418VpT9jV2fA25Alf2Le4KMLkMqvcwbxkg0uPS2BkTHvLk5ofpSelnBH96i9A== X-Received: by 10.66.181.16 with SMTP id ds16mr60049380pac.102.1473049172451; Sun, 04 Sep 2016 21:19:32 -0700 (PDT) Received: from Stas-Air.local (108-233-206-104.lightspeed.sntcca.sbcglobal.net. [108.233.206.104]) by smtp.gmail.com with ESMTPSA id i73sm11285893pfi.35.2016.09.04.21.19.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Sep 2016 21:19:31 -0700 (PDT) To: Davey Shafik , "internals@lists.php.net" References: Message-ID: <0b264e3e-ac31-35b3-083c-27adbb4ccd5e@gmail.com> Date: Sun, 4 Sep 2016 21:19:29 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove What would be achieved by this? I'm not sure about status of PEAR - frankly, didn't touch it for a long time - but if composer replaces most of it, it may be ok to remove by-default install of pear tools. Though I'm really not sure what "deprecating" means and what it's going to achieve. Pickle main README says: Pickle is a new PHP extension installer. It is based on Composer and the plan is to get Composer to fully support it. How is that plan going? I see the pull req it refers to still open, which means it is still not complete. Should it be completed before we recommend it as an only solution? > in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+) > in their place. Add in which meaning? Distribute composer package with PHP source? Wouldn't that add maintenance load to keep it up-to-date? If that means get some way to d/l newest stable composer, e.g. when installing php, that probably would be a great idea. Does not require removing stuff though. -- Stas Malyshev smalyshev@gmail.com