X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from ncopa-desktop.alpinelinux.org (3.203.202.84.customer.cdi.no [84.202.203.3]) (using SSLv3 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nc@alpinelinux.org) by mail.alpinelinux.org (Postfix) with ESMTPSA id 42E4DDC014E for ; Wed, 20 Feb 2013 12:27:59 +0000 (UTC) Date: Wed, 20 Feb 2013 13:27:56 +0100 From: Natanael Copa To: Alpine Linux Development Subject: [alpine-devel] abuild and subpackage split functions Message-ID: <20130220132756.32eef5c7@ncopa-desktop.alpinelinux.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.15; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, I have been thinking of adding support for new way of defining split functions for subpackages. Basically, use the subpackage name as is but with the forbidden chars (-, + and .) changed to an underscore. eg: pkgname="foo-pkg" subpackages="$pkgname-subpkg py-$pkgname" ... foo_pkg_subpkg() { ... } py_foo_pkg() { ... } What I am trying to accomplish is to simplify, so it is easy to understand what is going on. We will need to continue support the way it works now, for compatibility. What do you think about a such change? will it make things simpler or more confusing? The fact that we need compatibility makes me think it will complicate things more than simplify. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---