From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: PATCH: complete Debian architectures in common function
Date: Sat, 11 Oct 2014 02:27:39 +0200 [thread overview]
Message-ID: <20141011002739.GT5405@sym.noone.org> (raw)
In-Reply-To: <10081.1412983064@thecus.kiddle.eu>
Hi Oliver,
On Sat, Oct 11, 2014 at 01:17:44AM +0200, Oliver Kiddle wrote:
> Quite a few of the Debian completions need to complete the Debian
> architectures. This factors that out into _deb_architectures.
Indeed. Thanks!
A few thoughts:
> +_description architectures expl 'architecture'
> +compadd "$@" "$expl[@]" alpha amd64 arm64 armel armhf hppa hurd-i386 i386 ia64 \
> + kfreebsd-amd64 kfreebsd-i386 m68k mips mipsel powerpc powerpcspe ppc64 \
> + ppc64el s390x sh4 sparc sparc64 x32 ${=extra[2]}
I wonder how much sense it may make to use the output of
"dpkg-architecture -L" as values.
While it would make the list always being uptodate, it would not work
on systems where dpkg-dev is not installed, especially not on
non-debianoid systems. And the list contains way more fictional (i.e.
potential future) architectures (> 400) than really existing
architectures.
OTOH I don't miss much in the above list and a hardcoded list is
surely faster than depending on some command's output.
>From a first glance the no more supported s390 and lpia (the latter
was Ubuntu-only) and the never taken off avr32 are missing, but then
again omitting no more existing architectures may be on purpose.
A potential compromise would be using "dpkg-architecture -L | fgrep -v
-- -" plus the three non-linux architectures listed above.
The output of the command (without the three non-linux architectures
added) gives us:
alpha
amd64
arm
arm64
armeb
armel
armhf
avr32
hppa
i386
ia64
m32r
m68k
mips
mips64
mips64el
mipsel
mipsn32
mipsn32el
or1k
powerpc
powerpcel
powerpcspe
ppc64
ppc64el
s390
s390x
sh3
sh3eb
sh4
sh4eb
sparc
sparc64
x32
Then again even the full list doesn't include the architecture
"illumos-amd64" as used on http://apt.osdyson.org/dists/lacaille/main/.
(Dyson is a project which tries port Debian onto the Illumos kernel.
The project even maintains a derivative of Debian's zsh package at
http://cgit.osdyson.org/zsh.git/! :-)
So maybe we should just merge the list above into the hardcoded one by
Oliver, maybe omitting some no more existing architectures and adding
illumos-amd64.
Kind regards, Axel
--
/~\ Plain Text Ribbon Campaign | Axel Beckert
\ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail)
X See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber)
/ \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)
prev parent reply other threads:[~2014-10-11 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 23:17 Oliver Kiddle
2014-10-11 0:27 ` Axel Beckert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141011002739.GT5405@sym.noone.org \
--to=abe@deuxchevaux.org \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).