| 1 |
On Tue, 11 Oct 2011 12:36:15 -0700 |
| 2 |
Alec Warner <antarus@g.o> wrote: |
| 3 |
|
| 4 |
> On Tue, Oct 11, 2011 at 12:23 PM, Francisco Blas Izquierdo Riera |
| 5 |
> (klondike) <klondike@g.o> wrote: |
| 6 |
> > El 11/10/11 20:55, Markos Chandras escribió: |
| 7 |
> >> On 10/11/11 19:50, Francisco Blas Izquierdo Riera (klondike) wrote: |
| 8 |
> >> > Hi, |
| 9 |
> >> |
| 10 |
> >> > Today I have found that build dependencies are left in the system |
| 11 |
> >> > but won't be upgraded when running emerge -vauD1 world. This can |
| 12 |
> >> > be inconvenient since security issues fixed in those left over |
| 13 |
> >> > packages won't be applied properly. So, is there any reason for |
| 14 |
> >> > this behaviour? Shouldn't build dependencies either be cleaned |
| 15 |
> >> > with --depclean after building or be upgraded to avoid possible |
| 16 |
> >> > issues? |
| 17 |
> >> |
| 18 |
> >> > Sorry if this gets in here twice, I used an incorrect account. |
| 19 |
> >> |
| 20 |
> >> |
| 21 |
> >> Maybe you want the --with-bdeps parameter along with the -D one?. |
| 22 |
> >> man emerge -> section Options -> parameter -D |
| 23 |
> > That makes sense but then the problem is on the poor documentation |
| 24 |
> > we have in the Internet. |
| 25 |
> > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 |
| 26 |
> > Here no mention to that option is made |
| 27 |
> > Nor is in: |
| 28 |
> > http://www.gentoo.org/doc/en/gentoo-upgrading.xml |
| 29 |
> > |
| 30 |
> > And in fact no mention to the option is made in the doc space at |
| 31 |
> > all. I may also be wrong here but I don't recall finding it when I |
| 32 |
> > started with portage and no notice was issued since then so either |
| 33 |
> > I misunderstood it, kinda likely by then, or it was added later. |
| 34 |
> > And the fact it wasn't commented at all in the documentation didn't |
| 35 |
> > help. |
| 36 |
> > |
| 37 |
> > The question now is anybody thinks this shouldn't appear in the |
| 38 |
> > handbook? If nobody has a problem I'll prepare a patch. |
| 39 |
> > |
| 40 |
> > PS: howarang thanks for the point I found it really odd this was |
| 41 |
> > missing. |
| 42 |
> > |
| 43 |
> > |
| 44 |
> |
| 45 |
> FYI: there are a truckload of options that are available in portage |
| 46 |
> but are not documented in the handbook. I'm not really sure |
| 47 |
> replicating the portage manpages in the handbook is necessarily a good |
| 48 |
> way to move forward. Ideally we would direct users to just read the |
| 49 |
> manpages. |
| 50 |
|
| 51 |
Or go with a saner defaults... |
| 52 |
|
| 53 |
-- |
| 54 |
Best regards, |
| 55 |
Michał Górny |
Archives