| 1 |
On Wednesday 11 August 2004 06:22, Marius Mauch wrote: |
| 2 |
> |
| 3 |
> That leaves us with option b): We already offer tarballs of the portage |
| 4 |
> tree, including the tarballs used to create our releases. People even |
| 5 |
> have to use them if they want to use GRP. As people already know how to |
| 6 |
> use them I'd suggest that we use tarballs to provide our frozen tree |
| 7 |
> (wether we use the existing ones or create special ones is open for |
| 8 |
> discussion). As this GLEP is looking for a long-term solution we can |
| 9 |
> probably rely on some portage modifications that will be included in the |
| 10 |
> version after 2.0.51 that will enhance our `emerge sync` mechanisms |
| 11 |
> greatly (removing the need for emerge-webrsync and gensync). With these |
| 12 |
> modifications we can set SYNC to our tarball and offer updates over |
| 13 |
> rsync/cvs/tarballs/other transport that will be stored in an overlay, |
| 14 |
> that overlay can then by synced with `emerge --sync updates` ("updates" |
| 15 |
> is just an example, we can use any name there). |
| 16 |
> (Anyone interested in the details of the modification see bug 35535). |
| 17 |
|
| 18 |
What I see in this discussion is one thing. We really need to have ebuilds |
| 19 |
specify the auxiliary files they use (the files in the files directory except |
| 20 |
digest). Using such a AUX_FILES variable it is possible to automatically make |
| 21 |
a tree containing only one stable ebuild version per slot (with checked |
| 22 |
deps). It also allows keeping track of which files are still in actual use. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives