1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hi, |
5 |
|
6 |
I've received number of emails from people who are interested in |
7 |
working on "tags support" as an soc project (I've added 8 people as |
8 |
bcc recipients of this email). However, I think that this project is |
9 |
inappropriate for soc because it is too trivial. Once we've decided |
10 |
on the method that tags will be expressed (metadata.xml or a new |
11 |
variable in ebuilds), adding support for it to just about any tool |
12 |
should only amount to approximately 1 or 2 hours of work (pretty |
13 |
trivial). |
14 |
|
15 |
Anyway, the first step to adding tag support is to propose a |
16 |
specification to the gentoo-dev mailing list. There has already been |
17 |
some recent discussion on this topic [1]. Typically, extensions like |
18 |
this are proposed as a GLEP before they are implemented. For |
19 |
example, a recent extension that is similar in scope to tags was |
20 |
glep 56 [3]. |
21 |
|
22 |
[1] |
23 |
http://archives.gentoo.org/gentoo-dev/msg_49d13fd1a36cdf2464df7e99ab05b44c.xml |
24 |
[2] http://www.gentoo.org/proj/en/glep/glep-0001.html |
25 |
[3] http://www.gentoo.org/proj/en/glep/glep-0056.html |
26 |
- -- |
27 |
Thanks, |
28 |
Zac |
29 |
-----BEGIN PGP SIGNATURE----- |
30 |
Version: GnuPG v2.0.10 (GNU/Linux) |
31 |
|
32 |
iEYEARECAAYFAknJcJkACgkQ/ejvha5XGaOJ8gCgxVmqyAdDykGY8eeHxlYfHsS+ |
33 |
vMAAoLXu80VT7BGusPZioLuzM4pnEpzl |
34 |
=CYqA |
35 |
-----END PGP SIGNATURE----- |