From: "josé Alberto Suárez López" <bass@gentoo.org>
To: gnap-dev@lists.gentoo.org
Subject: [gnap-dev] Steps to GNAP 3
Date: Mon, 26 May 2008 10:25:24 +0200 [thread overview]
Message-ID: <1211790324.1265.22.camel@supercoco> (raw)
Now we have the new repos (svn) on google we can start the fun:
1. Repos structure
code (related gnap code)
|_scripts (realted scripts)
snapshots (minimal portage tree, stages and so on)
|_portage-min
|_portage-gnap (specific gnap ebuilds)
|_portage-extra (some extra ebuilds)
|_portage-sources (sources of ebuilds in portage-*)
|_[min,gnap,extra] (subdirs)
|_seedstage-uclibc (stages to use in gnap creation)
|_seedstage-glibc
gnap-core (ready to use gnap)
|_(subdirs)
2. code upgrade & cleanup
We need to merge all the code created in last GSoC in the new repos
3. update portage-min
4. we need to meet (on irc)
any comment is welcome
PD: please if you are interested in but don't have any comment just say
hi to know you are alive :)
--
gnap-dev@lists.gentoo.org mailing list
next reply other threads:[~2008-05-26 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 8:25 josé Alberto Suárez López [this message]
2008-05-26 14:45 ` [gnap-dev] Steps to GNAP 3 Andrey Falko
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=1211790324.1265.22.camel@supercoco \
--to=bass@gentoo.org \
--cc=gnap-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