X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com [209.85.219.220]) by lists.alpinelinux.org (Postfix) with ESMTP id AB8101EB587 for ; Thu, 11 Feb 2010 22:13:56 +0000 (UTC) Received: by ewy20 with SMTP id 20so2016422ewy.20 for ; Thu, 11 Feb 2010 14:13:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ocrOm/NWgLpVw5+1AwyuV04RF4b3u3Ny/qI0fMXR+fs=; b=kxCFr/nrzm0uTzzM4Pqxu1K9ne9tlRj++7420T0z7Ur9bs5Na+Z6k0V1xHvrtrDr8W 0Lmg+40y7wfsDoNXq6oM8fuuFhzGpxI3xRs82YwcwgWS874WdLU5Roo6IBrb3yQxd5yi i3ElB4jSulV9SfvcYH+GNYmqD6xk3fzjZTbbQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xeTYyW8VzOKsj6O3PW1tnWxX5W7i/A0Cp1kMfZi7lHSQZMV+09d3LrrAyPoRLB28F9 Mds6N/SFnMA7m5X5V149fs9ciu3gBemAw67rBsZdX/SFyIzk9bg+DmUwX8IscpPSGrzT Mw35XnKH4dXURKAjR1K0clqzybYryIH2zNBDc= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.216.85.143 with SMTP id u15mr296131wee.205.1265926435326; Thu, 11 Feb 2010 14:13:55 -0800 (PST) In-Reply-To: <95408c821002110703u72a33179w43df88d1902c9fc@mail.gmail.com> References: <95408c821002110703u72a33179w43df88d1902c9fc@mail.gmail.com> Date: Thu, 11 Feb 2010 16:13:55 -0600 Message-ID: <531b02ea1002111413k10d4decfl58acd052184a7be6@mail.gmail.com> Subject: Re: [alpine-devel] apk-tools/dependencies question for php From: Cameron Banta To: Natanael Copa Cc: Alpine Developers Content-Type: multipart/alternative; boundary=0016e6da7db87d4cdd047f5a771b --0016e6da7db87d4cdd047f5a771b Content-Type: text/plain; charset=ISO-8859-1 On Thu, Feb 11, 2010 at 9:03 AM, Natanael Copa wrote: > So we have this package, php, which raises interesting questions about > dependencies. > > we have 'php-cli', 'php' (php-cgi) and various php modules. Lets use > php-gd as an example. > > php-imap does not make sense as a standalone, its just a .so file, so > it made sense to have 'php' as a dependency. You installed php-gd, it > pulled in php for you. > > Now that we have php-cli in addition to php (cgi), and you can run > either of those with php-imap we can no longer pull in 'php' as > dependency since you might want to run the php-cli and not the cgi. > > so how do we deal with that? > > I can see those options: > > 1. remove the php dependency from php-dg (and all other php modules) > and let user handle the deps himself > 2. implement optional/volunteer dependencies in apk-tools. You can as > user do something to tell apk that we want php-gd to be a dependency > for php when you install php, so when php is removed php-gd goes out > as well. > 3. some other way to snap in dependencies manually afterwards. Like: > # install php-gd and php-imap as dependencies for php > apk add -d php php-gd php-imap > 4. implement 'or' in apk-tools and let php-gd depend on either 'php or > php-cli' > > For now i think we will go for option 1, but it would be nice to hear > what you think would be the optimal solution for this situation. > > Another option similar to 4 - could we do some kind of provides? Kind of like openrc does. So php-cli would provide php. So if you installed php-gd, it would install php as dependency. But if you installed php-cli first, then php-gd wouldn't install anything extra because it would think php was already installed. -Cameron --0016e6da7db87d4cdd047f5a771b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Feb 11, 2010 at 9:03 AM, Natanael Copa <= span dir=3D"ltr"><natanael.co= pa@gmail.com> wrote:
So we have this package, php, which raises interesting questions about
dependencies.

we have 'php-cli', 'php' (php-cgi) and various php modules.= Lets use
php-gd as an example.

php-imap does not make sense as a standalone, its just a .so file, so
it made sense to have 'php' as a dependency. You installed php-gd, = it
pulled in php for you.

Now that we have php-cli in addition to php (cgi), and you can run
either of those with php-imap we can no longer pull in 'php' as
dependency since you might want to run the php-cli and not the cgi.

so how do we deal with that?

I can see those options:

1. remove the php dependency from php-dg (and all other php modules)
and let user handle the deps himself
2. implement optional/volunteer dependencies in apk-tools. You can as
user do something to tell apk that we want php-gd to be a dependency
for php when you install php, so when php is removed php-gd goes out
as well.
3. some other way to snap in dependencies manually afterwards. Like:
=A0# install php-gd and php-imap as dependencies for php
=A0apk add -d php php-gd php-imap
4. implement 'or' in apk-tools and let php-gd depend on either '= ;php or php-cli'

For now i think we will go for option 1, but it would be nice to hear
what you think would be the optimal solution for this situation.


Another option similar to 4 - could we= do some kind of provides? Kind of like openrc does.=A0

So php-cli would provide php. So if you installed php-gd, it would in= stall php as dependency. But if you installed php-cli first, then php-gd wo= uldn't install anything extra because it would think php was already in= stalled.

-Cameron
--0016e6da7db87d4cdd047f5a771b-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---