| 1 |
On Wed, Jun 14, 2017 at 1:06 PM, William Hubbs <williamh@g.o> wrote: |
| 2 |
> On Wed, Jun 14, 2017 at 07:00:05PM +0200, Michał Górny wrote: |
| 3 |
>> On śro, 2017-06-14 at 11:11 -0500, William Hubbs wrote: |
| 4 |
>> > All, |
| 5 |
>> > |
| 6 |
>> > I am about to write two new ebuilds for packages for Gentoo that are for |
| 7 |
>> > container-related utilities. |
| 8 |
>> > |
| 9 |
>> > Currently, the best place to put them would be app-emulation, or |
| 10 |
>> > app-misc or dev-util, probably app-emulation would be my first choice. |
| 11 |
>> > |
| 12 |
>> > Is it time to start thinking about an app-containers category? |
| 13 |
>> > If so, is it ok for me to start an app-containers category with these |
| 14 |
>> > packages then we can look into moving other packages to it? |
| 15 |
>> > |
| 16 |
>> |
| 17 |
>> You don't create a new category for two packages. Do you have more use |
| 18 |
>> cases for it? I think usually people provide a fair number of existing |
| 19 |
>> packages that are in different categories to prove the necessity |
| 20 |
>> of a new category. |
| 21 |
> |
| 22 |
> I know this, that is why I brought it up actually. I'm working on these |
| 23 |
> ebuilds and was going to pre-empt a package move for them by opening up |
| 24 |
> a discussion about a category now. |
| 25 |
> |
| 26 |
> There are multiple packages under app-emulation that are container |
| 27 |
> related vs emulation/vm related that could be moved and there is one at |
| 28 |
> least under dev-util (dev-util/docker-ls). |
| 29 |
> |
| 30 |
|
| 31 |
Some likely candidates for the new category (excerpt from eix -S container): |
| 32 |
|
| 33 |
* app-emulation/docker |
| 34 |
Description: The core functions you need to create Docker |
| 35 |
images and run Docker containers |
| 36 |
|
| 37 |
* app-emulation/docker-compose |
| 38 |
Description: Multi-container orchestration for Docker |
| 39 |
|
| 40 |
* app-emulation/docker-gc |
| 41 |
Description: Docker garbage collection of containers and images |
| 42 |
|
| 43 |
* app-emulation/docker-machine |
| 44 |
Description: Machine management for a container-centric world |
| 45 |
|
| 46 |
* app-emulation/docker-proxy |
| 47 |
Description: Docker container networking |
| 48 |
|
| 49 |
* app-emulation/docker-runc |
| 50 |
Description: runc container cli tools (docker fork) |
| 51 |
|
| 52 |
* app-emulation/flannel |
| 53 |
Description: An etcd backed network fabric for containers |
| 54 |
|
| 55 |
* app-emulation/lxc |
| 56 |
Description: LinuX Containers userspace utilities |
| 57 |
|
| 58 |
* app-emulation/lxd |
| 59 |
Description: Fast, dense and secure container management |
| 60 |
|
| 61 |
* app-emulation/rkt |
| 62 |
Description: rkt is an App Container runtime for Linux |
| 63 |
|
| 64 |
* app-emulation/runc |
| 65 |
Description: runc container cli tools |
| 66 |
|
| 67 |
* app-emulation/s6-overlay |
| 68 |
Description: an s6-based init system for containers |
| 69 |
|
| 70 |
* dev-util/docker-distribution-pruner |
| 71 |
Description: Clean all old container revisions from registry |
| 72 |
|
| 73 |
* sys-apps/lmctfy |
| 74 |
Description: Linux application container management from Google |
| 75 |
|
| 76 |
* sys-cluster/singularity |
| 77 |
Description: Application containers for Linux |
| 78 |
|
| 79 |
* sys-cluster/vzctl |
| 80 |
Description: OpenVZ ConTainers control utility |
Archives