directory-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [directory-discuss] Antifeatures - Names with Controversial Terms: l


From: Ian Kelling
Subject: Re: [directory-discuss] Antifeatures - Names with Controversial Terms: linux
Date: Fri, 16 Dec 2016 18:45:53 -0800

On Mon, Nov 21, 2016, at 01:55 AM, David Hedlund wrote:
> I ran this in Trisquel 7 to find out how often the term "linux" is
    misused in package titles: 
> sudo apt-cache search --names-only linux | cut -f1 -d " " | grep
        linux | grep -v "\-gnu" | grep -v "linux\-cloud\-tools" | grep
        -v "linux\-generic" | grep -v "linux\-headers" | grep -v
        "linux\-image" | grep -v "linux\-lowlatency" | grep -v
        "linux\-lts" | grep -v "linux\-tools" | grep -v "selinux" | sort
        > linux-named.txt


> 
> We need to inform the developers that they should change the package
    name to help us stop confuse their work with the Linux kernel. Do do
    that I need a a team to put " - whitelist" or " - blacklist" after
    each package, then I will add the blacklisted packages to the FSD
    and add [[Category:Category:Names with
      Controversial Terms antifeature]]:
>  
>  autorun4linuxcd
>  circuslinux
>  circuslinux-data
>  dahdi-linux
>  doc-linux-fr-html
>  doc-linux-fr-pdf
>  doc-linux-fr-ps
>  doc-linux-fr-text
>  doc-linux-hr
>  doc-linux-ja-html
>  doc-linux-ja-text
>  doc-linux-pl
>  doc-linux-pl-html
>  efilinux
>  ekeyd-egd-linux
>  extlinux
>  focalinux-html
>  focalinux-text
>  fonts-linuxlibertine
>  ganglia-modules-linux
>  gcc-arm-linux-androideabi
>  gcc-i686-linux-android
>  golang-go-linux-386
>  golang-go-linux-amd64
>  golang-go-linux-arm
>  grub-linuxbios
>  lcd4linux
>  libcorelinuxc2a
>  libcorelinux-dev
>  libcorelinux-doc
>  libcorelinux-examples
>  libhbalinux2
>  libhbalinux-dev
>  liblinux-distribution-packages-perl
>  liblinux-distribution-perl
>  liblinux-dvb-perl
>  liblinux-epoll-perl
>  liblinux-inotify2-perl
>  liblinux-io-prio-perl
>  liblinux-kernelsort-perl
>  liblinux-lvm-perl
>  liblinux-prctl-perl
>  liblinux-usermod-perl
>  libsocket-linux-perl
>  libsys-statistics-linux-perl
>  linux-base
>  linux-crashdump
>  linuxdcpp
>  linux-doc
>  linuxdoc-tools
>  linuxdoc-tools-info
>  linuxdoc-tools-latex
>  linuxdoc-tools-text
>  linux-hwe-generic-trusty
>  linux-hwe-virtual-trusty
>  linux-igd
>  linuxinfo
>  linux-libc-dev
>  linux-libc-dev-arm64-cross
>  linux-libc-dev-armel-cross
>  linux-libc-dev-armhf-cross
>  linux-libc-dev-powerpc-cross
>  linux-libc-dev-ppc64el-cross
>  linuxlogo
>  linux-patch-xenomai
>  linux-server
>  linux-sound-base
>  linux-source
>  linux-source-3.13.0
>  linux-user-chroot
>  linux-user-chroot-dbg
>  linux-virtual
>  linux-virtual-lts-utopic
>  linux-virtual-lts-wily
>  linuxvnc
>  llk-linux
>  mplinuxman
>  neutron-plugin-linuxbridge
>  neutron-plugin-linuxbridge-agent
>  pptp-linux
>  qtcreator-plugin-remotelinux
>  qtcreator-plugin-remotelinux-dev
>  syslinux
>  syslinux-common
>  syslinux-legacy
>  syslinux-themes-debian
>  syslinux-themes-debian-squeeze
>  syslinux-themes-debian-wheezy
>  syslinux-themes-ubuntu
>  syslinux-themes-ubuntu-oneiric
>  syslinux-themes-ubuntu-precise
>  syslinux-themes-ubuntu-quantal
>  syslinux-themes-ubuntu-raring
>  syslinux-themes-ubuntu-saucy
>  syslinux-themes-ubuntu-trusty
>  util-linux
>  util-linux-locales
>  walinuxagent
>  walinuxagent-data-saver
>  wraplinux
>  wraplinux-dbg


Quite a few of these packages are related to the linux kernel, which is
not a problematic term.

And even if it is a reference to the "linux system" which we recommend
people avoid using, it's a part of a name that means something
else. Like "new york", is basically never used in reference to how "new"
it is, and when we say GNU, we are almost never saying how much like or
unlike unix it is, "syslinux" is the same way.

As RMS says, this is not worth contacting the developers about, and that
being the case, it also does not make sense to have a big red banner
warning, calling it an antifeature, and implying people should look for
an alternative.

I'm going to remove it.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]