X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 8D2815C5C15 for ; Tue, 27 Nov 2018 11:43:29 +0000 (GMT) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 500F59E20B2; Tue, 27 Nov 2018 11:43:29 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 3701A9E1D24; Tue, 27 Nov 2018 11:43:26 +0000 (GMT) Date: Tue, 27 Nov 2018 12:43:22 +0100 From: Natanael Copa To: Bobby Bingham Cc: Timo Teras , Steffen Nurpmeso , alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] apk: package "grouping"? Message-ID: <20181127124322.23d7aba7@ncopa-desktop.copa.dup.pw> In-Reply-To: <20181113181245.GA15037@gordon> References: <20181113150523.6IZfu%steffen@sdaoden.eu> <20181113191851.1fec6483@vostro> <20181113181245.GA15037@gordon> X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-alpine-linux-musl) 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 On Tue, 13 Nov 2018 12:12:45 -0600 Bobby Bingham wrote: > On Tue, Nov 13, 2018 at 07:18:51PM +0200, Timo Teras wrote: > > Hi, > > > > I generally do my own meta-packages and host internal repository. This > > allows also updating the meta-packages pretty easily. > > > > Doing apk/world.d/ or similar is an interesting idea too. But I need to > > think about it more. Mostly it's if there's an use case where this > > works better than the meta-packages in own repository. > > > > Thoughts? > > This sounds a lot like the concept of package sets in portage, and is > one of the things I miss the most coming from Gentoo. > > One place I find it useful is when trying to build a piece of software > that isn't packaged. I need to install a number of *-dev packages that > I'll just uninstall after I get the build working. There may be a large > number of them, and I may keep discovering more dependencies as I go, > both of which make it harder to keep track of the packages to uninstall > at the end. By adding them via a package set, it becomes trivial to > just uninstall the whole set at the end. I use `apk add --virtual .mydeps foo-dev bar-dev` and when done: `apk del .mydeps` for this. But it seems like you cannot append deps afterwards. > > I do have a local package repository, but creating a throw away package > whose entire purpose is to be easy to uninstall has always seemed like > overkill. > > -- > Bobby > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- > --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---