X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail.squbes.com (squbes.com [208.74.142.49]) by lists.alpinelinux.org (Postfix) with ESMTP id 4DD3F1EB587 for ; Mon, 8 Mar 2010 02:47:37 +0000 (UTC) Received: from serenity.local (c-76-30-54-60.hsd1.tx.comcast.net [76.30.54.60]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: nangel@tetrasec.net) by mail.squbes.com (Postfix) with ESMTPSA id 58E5950001CAD for ; Mon, 8 Mar 2010 02:47:36 +0000 (UTC) Message-ID: <4B946547.7090100@nothome.org> Date: Sun, 07 Mar 2010 21:47:35 -0500 From: Nathan Angelacos User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 To: Alpine Developers Subject: Re: [alpine-devel] apk-tools idea: runtime plugins References: <95408c821003012340w72402e30mbf177585e74bede7@mail.gmail.com> <4B8CDE8F.2030703@iki.fi> In-Reply-To: <4B8CDE8F.2030703@iki.fi> Content-Type: text/plain; charset="iso-8859-1"; format="flowed" Content-Transfer-Encoding: quoted-printable On 3/2/10 4:46 AM, Timo Ter=E4s wrote: > Natanael Copa wrote: >> Other idea I have been thinking for some time: runtime plugins for >> apk-tools >> >> What triggered this idea was that it would be nice to have a "real" >> http/ftp downloader via curl or similar instead of fork/exec bb wget, >> however, would not be nice to need libcurl in the initramfs image. >> >> Some options: >> We could have fetcher plugins. install /lib/apk/fetch_curl.so and >> suddenly you have http and ftp support. Install /lib/apk/fetch_scp.so >> and suddenly apk-tools understands scp:// repositories. >> Does the extra functionality outweigh the complexity? apk is still relatively simple. simple is good. >> We could have applet plugins. Install /lib/apk/index.so and you get >> 'apk index' etc. >> >> In future we could have /lib/apk/gtk-progress-bar.so etc... >> >> Other option is that we could have only one plugin that have all the >> "extended" stuff. So you have an apk-tools-base or similar, containing >> only the basic functionallity, apk add, apk del and thats it. It could >> use the busybox wget to fetch from http. Then you have another package >> apk-tools-extras or similar that includes plugins for http download >> via curl, includes the developer stuff like apk index etc. > > Might be an idea. However, I'm not currently sure what extra benefit > we get from using libcurl or wget. Splitting the applets to separate > modules might be useful though. > >> In any case, it would be nice to be able have a framework for runtime >> plugins. > > Yes, the more modular code we do, the easier it is to extend it later. > > Patches are welcome :) > > - Timo ok.. refactoring apk so that plugins are easier is one thing... but=20 still not convinced on the value vs effort(code+bug reports) on the=20 plugin part. --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---