Re: [gentoo-portage-dev] New emerge --mindeps option for exclusion of build time dependencies (bug #132355)

[Zac Medico]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ned Ludd wrote:
> On Wed, 2006-07-12 at 08:22 -0700, Zac Medico wrote:
> > Ned Ludd wrote:
> > >> Please invert the logic so that rather than changing default behavior
> > >> you add a new option choose the types of deps to include.
> >
> > Can you explain how my proposed change in the default behavior of
> > --usepkg is going to hurt things? The current default behavior is
> > inconsistent because build time dependencies are considered for
> > packages that are installed but not for binary packages that are about
> > to be installed.
>
> And nor should they be unless the user explicitly asks for it.
> There basically should be no valid reason to look at build
> deps as we are dealing with a binary pkg because the package
> is already built.

Updates are most often performed from source, are they not?  If the build deps are already merged then they'll be ready and waiting for the next source based update or rebuild.

> > >> export ACCEPT_DEPENDS="DEPEND RDEPEND PDEPEND"
> > >> emerge -K system
> >
> > While I admire the flexibility of your ACCEPT_DEPENDS proposal, I feel
> > that it exposes far too much complexity to the user.
>
> Really? To me it would seem very natural to the Gentoo user who is
> already familiar with ACCEPT_KEYWORDS.

For the type of functionality that we're after, a simple boolean option should suffice. ACCEPT_DEPENDS exposes implementation details that go far beyond the required information. For example, RDEPEND and PDEPEND can actually be collapsed together, so DEPEND and RDEPEND are the only real choices that are currently available.

> To me it seems like the wrong fix for the problem at hand and
> changes portage's default behavior in an undesired way.
> Don't get me wrong I'm definitely in favor of finer grained control
> over all the dep handling in general, but don't think this option
> should become the default. I'd invert your logic like in Kumba's
> proposed patch did and run with that.

What about this functionality as it applies to packages that are already installed?  If we invert the logic in that case, build deps will no longer be considered by default when the user runs `emerge -uD world` or `emerge --depclean`.  That's an even larger change in behavior and, like I said in my reply to Drake, I'm afraid that it would cause lots of complaints and/or bugs filed. My proposed change will provide consistency in all cases with a change in the default --usepkg behavior that I feel will be acceptable to the vast majority of portage users.

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)

iD8DBQFEtTz//ejvha5XGaMRAk+uAJ9PwwvS9tOupY8K8g661FHF92vinQCgw9t/
GUsyhoTbR0GDpzxOsVFTfgE=
=D6MW
-----END PGP SIGNATURE-----
-- 
gentoo-portage-dev@g.o mailing list