Date: Tue, 13 Nov 2018 19:54:31 +0100
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Timo Teras <timo.teras@iki.fi>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] apk: package "grouping"?
Message-ID: <20181113185431.JCuei%steffen@sdaoden.eu>
In-Reply-To: <20181113191851.1fec6483@vostro>
References: <20181113150523.6IZfu%steffen@sdaoden.eu>
 <20181113191851.1fec6483@vostro>
Mail-Followup-To: Timo Teras <timo.teras@iki.fi>,
 alpine-devel@lists.alpinelinux.org
User-Agent: s-nail v14.9.11-76-g38917986
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD;
 url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
 the world can make no bugs.
Precedence: list

Timo Teras wrote in <20181113191851.1fec6483@vostro>:
 |I generally do my own meta-packages and host internal repository. This
 |allows also updating the meta-packages pretty easily.

I do not really understand the latter (i still struggle how i can
share the binary cache in between the machines, but i will find
out).

The former i thought about too, but of course you need to create
meta packages in one go, if i understand it correctly.  This
does not work if you add in packages later, for example, about 15
minutes ago i had to add in "kbd" to gain some more Unicode
characters on the Linux framebuffer.  Now i need this over there,
too ...

 |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.

Host internal repository and binary cache, i will look around
this.  Thanks.

 |Thoughts?

Well...  No.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---