| 1 |
E3 that's the editor written in assembler right ? |
| 2 |
I will just make vim part of the base system tarball for the alpha port, |
| 3 |
other items will of course have to change also, no more grub or lilo, and I |
| 4 |
will have to add milo for booting. |
| 5 |
I will continue to play with the latest snapshots. |
| 6 |
|
| 7 |
I also had an idea, for people stuck behind a nasty firewall, or no internet |
| 8 |
connection, that want to build everything. |
| 9 |
|
| 10 |
Have a special build cd, that has a 'snapshot' of the distfiles needed for a |
| 11 |
build, and emerge system. And the snapshot from cvs equivolent to whats on |
| 12 |
the disk. I have been using this method, on a couple of boxes at work, and |
| 13 |
it seems to work well for me. I use the build cd as a base, and just add the |
| 14 |
build tarball, and cvs tarball along with the distfiles. |
| 15 |
|
| 16 |
Joe |
| 17 |
|
| 18 |
> > I have recently set up an alpha machine running rh 7.1. I would like to |
| 19 |
port |
| 20 |
> > gentoo to the alpha chipset. My questions: Are there any parts of the |
| 21 |
> > portage tree that are binary ? Would it make more sense to start from |
| 22 |
rc6 |
| 23 |
> > build or rc5 build ? |
| 24 |
> |
| 25 |
> Um; the e3 editor won't work for you. That's a minor issue. Other than |
| 26 |
that, |
| 27 |
> you should be OK. Start with an rc6 build image in about a week. |
| 28 |
> |
Archives