Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: "William L. Thomson Jr." <wlt-ml@××××××.com>
Cc: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Package file name requirement for binary ebuilds
Date: Mon, 17 Oct 2016 06:57:48
Message-Id: 20161017085730.4f5589a2.mgorny@gentoo.org
In Reply to: Re: [gentoo-dev] Package file name requirement for binary ebuilds by "William L. Thomson Jr."
1 On Sun, 16 Oct 2016 18:30:44 -0400
2 "William L. Thomson Jr." <wlt-ml@××××××.com> wrote:
3
4 > Part of the idea is to help differentiate the types of binaries in tree to
5 > hopefully get less binaries that are from source.
6 >
7 > To start I just wanted to see about a policy for -bin, the other stuff was
8 > just extra after -bin itself was a policy. Unless it made sense to develop it
9 > in full,
10 >
11 > -bin - Closed source binary ebuild
12 > -ebin - Self made binary from source
13 > -sbin - Binary ebuild of an open source package
14
15 Let's also add -c for C programs, and -cxx for C++ programs. -py for
16 pure Python stuff, -cpy when stuff includes extensions compiled in C,
17 -cxxpy extensions in C++. We should also have special -x86asm suffix
18 for packages that rely on non-portable x86 assembly, or maybe even
19 -x86asm-sse when they use some fancy instruction sets. And then don't
20 forget to add a suffix for license, for GUI library (because obviously
21 nobody wants GTK+ software on KDE systems, nor GTK+3 software on GTK+
22 systems).
23
24 --
25 Best regards,
26 Michał Górny
27 <http://dev.gentoo.org/~mgorny/>

Replies

Subject Author
Re: [gentoo-dev] Package file name requirement for binary ebuilds Ulrich Mueller <ulm@g.o>
Re: [gentoo-dev] Package file name requirement for binary ebuilds "William L. Thomson Jr." <wlt-ml@××××××.com>