From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need clear semantics for packages with binary entities
Date: Thu, 31 Dec 2015 01:14:13 +0100 [thread overview]
Message-ID: <56847355.6080504@gentoo.org> (raw)
In-Reply-To: <20151228182414.GB4303@web>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
trupanka@gmail.com schrieb:
| I’m suffering from the fact that users can distinguish packages
| containing binaries just by eye. There is no mechanism to allow/ignore
| such packages.
| 7. to be continued... I guess
7. fonts which come precompiled instead of being built from source (e.g.
through fontforge)
8. artwork which is pre-rendered to bitmap formats but originally sourced
from vector graphics (e.g. KDE icons)
9. packages which download additional binary things later (Android SDK,
hplip depending on your printer)
10. documentation which is downloaded as PDF but not as DocBook/TeX/... sources
11. ... (I'm sure there are more)
| I wonder if Gentoo’s devs can do something with the problem. I think
| it’s problem in source-based Linux distribution.
I believe that Debian uses the term "preferred form for modification" to
describe/categorize their builds in that regard.
Best regards,
Chí-Thanh Christopher Nguyễn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlaEc1UACgkQ+gvH2voEPRCi6QCeNFoY/NWU0zXqf8B/F2tm1ZaB
y7QAni7MdYwoOQHn/1xQd8x2lsB5zc4n
=yQrF
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-12-31 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 18:24 [gentoo-dev] Need clear semantics for packages with binary entities trupanka
2015-12-28 18:33 ` Michał Górny
2015-12-30 12:13 ` Kristian Fiskerstrand
2015-12-30 16:28 ` Zac Medico
2015-12-31 0:14 ` Chí-Thanh Christopher Nguyễn [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=56847355.6080504@gentoo.org \
--to=chithanh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox