1 |
2015-03-02 23:10 GMT-03:00 Philip Webb <purslow@××××××××.net>: |
2 |
|
3 |
> 150303 Andreas K. Huettel wrote: |
4 |
> > If you look at your world file, you should for each line |
5 |
> > be able to immediately say "yes I know what this is and I need it". |
6 |
> > Where "I need it" means "I need it directly" |
7 |
> > and *not* "I need it because some other package needs it". |
8 |
> > In most cases this means that libraries should not be in the world file. |
9 |
> > You'll rarely say "Yes I need Boost" : instead you may need LibreOffice |
10 |
> > and that needs Boost ... The smaller your world file, |
11 |
> > the more freedom portage has to resolve dependencies. |
12 |
> |
13 |
> I was going to comment that I had 3 'lib' pkgs in 'world', |
14 |
> but then checked via 'emerge -cpv <pkg>' |
15 |
> & found that all of them -- /sys-libs/readline ncurses zlib -- |
16 |
> were in fact requirements for eg bash python vim kdelibs cups LO , |
17 |
> so now I've removed them & hope it will simplify Portage activities a bit. |
18 |
> |
19 |
> -- |
20 |
> ========================,,============================================ |
21 |
> SUPPORT ___________//___, Philip Webb |
22 |
> ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
23 |
> TRANSIT `-O----------O---' purslowatchassdotutorontodotca |
24 |
> |
25 |
> |
26 |
> |
27 |
|
28 |
Just my 2 cents: AFAIK, only if you are developing a new software that |
29 |
requires a specific library (or some of them, like "opencv", for example, |
30 |
which might not have yet been pulled by any other package) , then, and only |
31 |
then, you might add them to "world". Then, when your software is ready, |
32 |
please ( ;-) ) create a package for distributing your work, with those |
33 |
libraries as dependencies, and remove them from "world", as they will be |
34 |
pulled in by such package. |
35 |
|
36 |
As already remembered on this thread, each case must be checked. |
37 |
|
38 |
Best regards, |
39 |
Francisco |