Re: Build dependencies and upgrades.
Michał Górny <[email protected]> Tue, 11 Oct 2011 21:56:46 +0200
| Newsgroups | gmane.linux.gentoo.devel,gmane.linux.gentoo.documentation |
|---|---|
| Organization | Gentoo |
| Message-ID | <[email protected]> |
On Tue, 11 Oct 2011 12:36:15 -0700 Alec Warner <[email protected]> wrote: > On Tue, Oct 11, 2011 at 12:23 PM, Francisco Blas Izquierdo Riera > (klondike) <[email protected]> wrote: > > El 11/10/11 20:55, Markos Chandras escribió: > >> On 10/11/11 19:50, Francisco Blas Izquierdo Riera (klondike) wrote: > >> > Hi, > >> > >> > Today I have found that build dependencies are left in the system > >> > but won't be upgraded when running emerge -vauD1 world. This can > >> > be inconvenient since security issues fixed in those left over > >> > packages won't be applied properly. So, is there any reason for > >> > this behaviour? Shouldn't build dependencies either be cleaned > >> > with --depclean after building or be upgraded to avoid possible > >> > issues? > >> > >> > Sorry if this gets in here twice, I used an incorrect account. > >> > >> > >> Maybe you want the --with-bdeps parameter along with the -D one?. > >> man emerge -> section Options -> parameter -D > > That makes sense but then the problem is on the poor documentation > > we have in the Internet. > > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 > > Here no mention to that option is made > > Nor is in: > > http://www.gentoo.org/doc/en/gentoo-upgrading.xml > > > > And in fact no mention to the option is made in the doc space at > > all. I may also be wrong here but I don't recall finding it when I > > started with portage and no notice was issued since then so either > > I misunderstood it, kinda likely by then, or it was added later. > > And the fact it wasn't commented at all in the documentation didn't > > help. > > > > The question now is anybody thinks this shouldn't appear in the > > handbook? If nobody has a problem I'll prepare a patch. > > > > PS: howarang thanks for the point I found it really odd this was > > missing. > > > > > > FYI: there are a truckload of options that are available in portage > but are not documented in the handbook. I'm not really sure > replicating the portage manpages in the handbook is necessarily a good > way to move forward. Ideally we would direct users to just read the > manpages. Or go with a saner defaults... -- Best regards, Michał Górny
signature.asc
(application/pgp-signature, 316 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iJwEAQEIAAYFAk6Un38ACgkQfXuS5UK5QB1RMQP8COYUw7FiVEylkwVMusBj0skK 2xnityk0jzJ7VgP4nL4LH6VIjzjXtUFSMTYahzZdC2MROu1Sk6jh4ifiZNyDcScO H4LSd77hztJkRKK7X38peQqFjh3h4zcd3fxUF0qlnAzACXT/fs9Rb5bx2y1er8oD +t1ct1qkeTRY531grGE= =JM2Q -----END PGP SIGNATURE-----