| 1 |
> Well, I may be obnoxious but I do a stage4 with catalyst (total 200 |
| 2 |
> packages or so) and then trim it down using unmerge, empty and rm in |
| 3 |
> the spec file to suite. |
| 4 |
|
| 5 |
Well, it looks like the way to go to me too. Maybe I'll try to use |
| 6 |
binary packages in oder to avoid the unmerge process. |
| 7 |
|
| 8 |
I thought that I would be able to install only the needed packages and |
| 9 |
dependencies only and have a system like LFS (Linux From Scratch). |
| 10 |
|
| 11 |
Thanks for the help! |
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
2007/7/11, Peter Stuge <peter@×××××.se>: |
| 16 |
> On Wed, Jul 11, 2007 at 09:53:48PM +0100, Marcelo Coelho wrote: |
| 17 |
> > How can I trim the package set that would be emerged together with |
| 18 |
> > the cron daemon or other packages? |
| 19 |
> |
| 20 |
> First, add -t to the emerge to get a tree view of the dependencies. |
| 21 |
> |
| 22 |
> Then there are a few options; either make your own ebuilds in an |
| 23 |
> overlay, or make your own profile which can be used to enforce some |
| 24 |
> packages or not, or finally just tweak the use flags. |
| 25 |
> |
| 26 |
> |
| 27 |
> > When emerging with the ROOT var (eg.: /var/system), the make.conf |
| 28 |
> > file that is used is the one that is located at that location (eg.: |
| 29 |
> > /var/system/etc/make.conf) ? |
| 30 |
> |
| 31 |
> /etc/make.conf I believe. ROOT may not have any make.conf. |
| 32 |
> |
| 33 |
> |
| 34 |
> > What normally are the packages that you guys use as minimal system? |
| 35 |
> |
| 36 |
> Well, I may be obnoxious but I do a stage4 with catalyst (total 200 |
| 37 |
> packages or so) and then trim it down using unmerge, empty and rm in |
| 38 |
> the spec file to suite. catalyst doesn't do cross yet AFAIK so if you |
| 39 |
> need that it's not really an option I guess. |
| 40 |
> |
| 41 |
> |
| 42 |
> //Peter |
| 43 |
> -- |
| 44 |
> gentoo-embedded@g.o mailing list |
| 45 |
> |
| 46 |
> |
| 47 |
-- |
| 48 |
gentoo-embedded@g.o mailing list |
Archives