| 1 |
On Wed, 2005-06-29 at 13:29 -0400, Christophe PEREZ wrote: |
| 2 |
> Le Wed, 29 Jun 2005 11:39:14 -0400, Christophe PEREZ a écrit : |
| 3 |
> |
| 4 |
> > So, I have to build 3 stages before livecd-stage1 ? |
| 5 |
> > Oh ! |
| 6 |
> > still 3 specs to study :-( |
| 7 |
> > I'll try that. |
| 8 |
> |
| 9 |
> Building, but, to build stage1, it is equal to use stage2 or |
| 10 |
> stage3 for 'source_subpath' ? |
| 11 |
|
| 12 |
Both will work, but I prefer a stage3 as a seed stage (source). This is |
| 13 |
simply because it has a complete environment. |
| 14 |
|
| 15 |
> And, another problem I always had, my portage distfiles is on a nfs mount, |
| 16 |
> and in my /etc/make.conf, I have DISTDIR=/download/Linux/gentoo/portage. |
| 17 |
> All works fine with my normal system. |
| 18 |
> |
| 19 |
> But, if I put this path in catalyst.conf : distdir, I can see that each |
| 20 |
> build downloads files (from internet) each time. (bind mount doesn't seem |
| 21 |
> to work on nfs, so directory is removed each time, so packages downloaded |
| 22 |
> again) |
| 23 |
> |
| 24 |
> So, I had to use another path. |
| 25 |
> It works, all builds take their packages in it, but now, I have each |
| 26 |
> package 2 times on my system. One in the new catalyst distdir, and one in |
| 27 |
> my normal portage distdir (nfs mount). |
| 28 |
> |
| 29 |
> I saw something like that in archives, but never understood if it could be |
| 30 |
> solved or not. |
| 31 |
> Does catalyst can't work with nfs mount ? |
| 32 |
|
| 33 |
No clue. I have no issues with it, but I mount the remote NFS mount |
| 34 |
to /usr/portage on my build box. I have no issues with the bind mount, |
| 35 |
either. |
| 36 |
|
| 37 |
-- |
| 38 |
Chris Gianelloni |
| 39 |
Release Engineering - Strategic Lead/QA Manager |
| 40 |
Games - Developer |
| 41 |
Gentoo Linux |
Archives