1 |
Hi, |
2 |
|
3 |
thanks for your work :) so please next time confirm things like this |
4 |
with me, in the last email i told you i was creating the repository and |
5 |
than i will wait last week for a reply about the name. I was creating |
6 |
this morning the new repository when i readed your email. |
7 |
|
8 |
El dom, 25-05-2008 a las 14:47 +0200, Philipp Riegger escribió: |
9 |
> Hi everybody! |
10 |
> |
11 |
> We just created gnap-dev on Google Code: |
12 |
> http://code.google.com/p/gnap-dev/ |
13 |
> So please drop us (Andrey or me) a line and we will add you to the |
14 |
> project. |
15 |
> |
16 |
> Furthermore we added gnap-dev as email address where all svn commits |
17 |
> will be sent. This is ok, i guess, because this is a development list. |
18 |
> And it is too much overhead to create an extra list for that. I filed a |
19 |
> bug to get these messages whitelisted: |
20 |
> https://bugs.gentoo.org/show_bug.cgi?id=223551 |
21 |
> |
22 |
> Next thing: I'd like to reorganize the repository and the ebuilds. I |
23 |
> would like to split it the other way around than they are at the moment. |
24 |
> I'd like to have: |
25 |
> |
26 |
> A) One ebuild called gnap, that installes all gnap_* scripts, |
27 |
> documentation and examples. |
28 |
> |
29 |
> B) ebuilds of the form gnap-x86-uclibc, gnap-x86-glibc, |
30 |
> gnap-x86-uclibc-hardened,... for each target we support containing a |
31 |
> seedstage, build gnap base fs, maybe prebuilt extensions and the portage |
32 |
> snapshot. We could controll the installation of prebuild extensions, |
33 |
> prebuilt base fs and maybe other stuff with USE-flags. We could also |
34 |
> split the portage snapshot into an extra ebuild in case multiple targets |
35 |
> share the same one. |
36 |
> |
37 |
> A should have regular version numbers, like 2.0, 2.1, whatever, B should |
38 |
> only have dates as version. |
39 |
> |
40 |
> Comments? |
41 |
> |
42 |
> Thanks, |
43 |
> Philipp |
44 |
> |
45 |
> |
46 |
> |
47 |
|
48 |
-- |
49 |
gnap-dev@l.g.o mailing list |