[aur-general] Cross-compilers naming scheme

Bartłomiej Piotrowski barthalion at gmail.com
Sat Dec 17 10:29:38 EST 2011


If someone hasn't spot it yet, we have mess with naming of
cross-compilers in [community]. Currently there are 3 schemes:
  1) $appname-$platform (gcc-avr and binutils-avr)
     The only problem I see is mingw32 (and related packages). While
{gcc,binutils}-mingw32 looks fine, I don't know what to do with
mingw32-pthreads, mingw32-runtime and mingw32-w32api.
  2) $platform-$appname (mingw32 packages)
     My favorite. Seems to be most readable (IMHO) and can be easily
applied to every cross-compiler.
  3) cross-$platform-$appname
     Probably as good as second option, but cross prefix is annoying me.

I've already discussed it with Alexander Rødseth, but Arch isn't a
project for a few people. What do you think? Which option is the best one?

-- 
Bartłomiej Piotrowski
Arch Linux Trusted User
http://archlinux.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20111217/1d5a944e/attachment-0001.asc>


More information about the aur-general mailing list