Re: [gentoo-dev] common ebuild mistakes

[William McArthur]

I'd like to add to the list-all-deps-including-packages-in-system
because long ago I wanted to install sys-apps/man before I had installed
the full system so that I could read man pages before I started my full
install. The problem was man requires a pager like less to work.

You can read the bug report here: 
http://bugs.gentoo.org/show_bug.cgi?id=6565

The end result was: man and less are both in system so that one does not 
  need to depend on the other as they will both be installed. I'm of the 
opinion this is the wrong choice but whatever, life goes on, I worked 
around the problem.

Sandy

Zach Welch wrote:
> Aron Griffis wrote:
>> George Shapovalov wrote:[Mon May 26 2003, 02:49:36PM EDT]
>>
>>> As such it makes sense to put some absolutely something basic in
>>> DEPEND for the package which does not have any apparent (as
>>> non-trivial, not bad-researched) dependencies. In that respect
>>> virtual/glibc perfectly fits the bill...
>>
>> DEPEND="" works just as well.  Since glibc is in the default
>> profile, there's no reason to list it as a dependency, just like we
>> can assume some basic shell utilities are present when the ebuild
>> is processed.
>>
>
> Depending on the degree you are talking here, I tend to disagree with
> the notion of not including some so call "basic" dependencies,
> because profiles can have variations that may include stripping out
> some core components.  As we move into the embedded realm, the
> definition of our "core profile" will need to be reduced, so adding
> full dependency information now is not necessarily a bad thing.
>
> Instead, we need to clarify a truly minimal system set of packages
> (such as libc) for which their dependency information need not be
> included. This will probably be taken up as part of the embedded
> project's efforts to scale the system down, so there is not pressure
> to do this now.


--
gentoo-dev@g.o mailing list