[gentoo-dev] Last rites: dev-python/pydiff
# Louis Sautier (2021-08-07) # No reverse dependencies, no upstream activity for more than 5 years, # failing tests with Python 3.10. Removal on 2021-09-06. dev-python/pydiff OpenPGP_signature Description: OpenPGP digital signature
Re: [gentoo-dev] RFC: new category for container related packages, instead of app-emulation
> > Categories themselves were not a design mistake. The design mistake is > using categories to permit conflicting package names. > > Categories are convenient. Sure, they're not perfect but they serve > their purpose to some degree and there's little harm in having them. > If you want to organize packages better, nobody's stopping you. Until > you've got a better and widespread replacement, I don't see why people > shouldn't be using categories as they see fit. > > The other part is something we could aim for fixing but so far most > developers seems to disagree with me, so there's no point in pursuing > that. > So how about improving categories instead? Rough idea: * introduce 1st, 2nd, 3rd class categories, categorized in metadata somewhere * 1st class is what you want in your world file (and default setting) * 2nd class is everything else * 3rd class is stuff that should never be in your world file (but still can be, if you want) Then tooling can (maybe output a warning but) default to highest class category if none is given. Examples: * 1st class: app-*, dev-lang, games-*, ... * 2nd class: dev-haskell, dev-perl, dev-php, dev-python, dev-texlive, media-libs, net-libs, sci-libs, ... * 3rd class: acct-*, perl-core, virtual -- Andreas K. Hüttel dilfri...@gentoo.org Gentoo Linux developer (council, toolchain, base-system, perl, libreoffice) signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] RFC: new category for container related packages, instead of app-emulation
On 8/6/21 11:58 AM, A Schenck wrote: > On 8/5/21 5:57 PM, Alec Warner wrote: >> On Thu, Aug 5, 2021 at 2:44 PM Georgy Yakovlev wrote: >>> Hi, >>> >>> We've been collecting more and more container related packages in >>> app-emulation/* >>> >>> What do you think about finally moving those packages to separate category? >> As always my opinion is that: >> >> (a) Categories were a design mistake. >> (b) The mistake is hard to fix. >> (c) It's basically low-value to try to 'correctly' categorize packages >> because of A. >> (d) Recategorizing means a bunch of stuff has to be updated. >> >> Do people actually care what category things are in? I just use >> --search or eix or whatever and the category is just this...bad >> concept we attach to packages for silly historical reasons.. > We particularly like categories, and especially the (mostly) two-level > concept in gentoo. `emerge --search` works for some things, but often > returns extra junk to filter through, when we know a project name, it's > easier to just `ls /usr/portage/dev-ruby/` and see if there's a `grpc` > package in it (upstream gem seems to force `-j12` for native > compilation, wondered if gentoo packagers had fixed that problem). > Also, the graphical portage interface we use (and barely maintain) has a > two-level category picker which even lets you select just the top-level > category and see what's under several of it's subcategories: > > kuroo two-level category picker Unsurprisingly the list dropped the image even though it was small. Here's an ancient screenshot of the two-level category-package view: https://a.fsdn.com/con/app/proj/kuroo/screenshots/Kuroo4-packages.png > > -A > > >> -A >> >>> probably app-containers/ >>> >>> Here's the tentative list, most tools have description attached for easier >>> review, 36 candidates so far, there may be more around, I only looked at >>> app-emulation. >>> >>> app-emulation/buildah - A tool that facilitates building OCI images >>> app-emulation/cadvisor - container analyzer >>> app-emulation/conmon - An OCI container runtime monitor >>> app-emulation/containerd - A daemon to control runC >>> app-emulation/containers-storage - containers/storage library >>> app-emulation/cri-o - OCI-based implementation of Kubernetes CRI >>> app-emulation/cri-tools - CLI and validation tools for CRI >>> app-emulation/crun - OCI Container Runtime fully written in C >>> app-emulation/distrobuilder - System container image builder for LXC and LXD >>> app-emulation/docker - Main offender >>> app-emulation/docker-bench-security - Test for best docker practices >>> app-emulation/docker-cli - Main offender cli >>> app-emulation/docker-compose - Multi-container orchestration for Docker >>> app-emulation/docker-credential-helpers - >>> app-emulation/docker-gc - Docker garbage collection of containers and images >>> app-emulation/docker-proxy - Docker container networking >>> app-emulation/docker-registry - >>> app-emulation/docker-swarm - >>> app-emulation/flannel - An etcd backed network fabric for containers >>> app-emulation/go-secbench - run and evaluate the docker security benchmark >>> app-emulation/img - Standalone Dockerfile and OCI container image builder >>> app-emulation/k3d - creates k3s clusters in docker >>> app-emulation/kompose - Tool to move from docker-compose to Kubernetes >>> app-emulation/lxc - A userspace interface for the Linux kernel containment >>> app-emulation/lxc-templates - >>> app-emulation/lxd - Fast, dense and secure container management >>> app-emulation/nerdctl - Docker-compatible CLI for containerd >>> app-emulation/podman - Main offender killer >>> app-emulation/reg - Docker registry v2 command line client >>> app-emulation/runc - another docker thing >>> app-emulation/s6-overlay - an s6-based init system for containers >>> app-emulation/sen - Terminal User Interface for docker engine >>> app-emulation/skopeo - Utility for operations on container >>> images/repositories >>> app-emulation/slirp4netns - User-mode networking for unpriv network >>> namespaces >>> app-emulation/snapd - Service and tools for management of snap packages >>> app-emulation/umoci - Manipulation tool for OCI images >>> >>> Those 4 are technically emulation related, so I'm not sure about category: >>> app-emulation/docker-machine >>> app-emulation/docker-machine-kvm >>> app-emulation/hyperd >>> app-emulation/runv
