Nirbheek Chauhan nirbh...@gentoo.org wrote:
That's because repoman is context-aware. When you use it, it'll look
around (../..) the current directory for the dependencies. If it
finds the deps, it'll check if the ebuilds. If can't find the
dependencies, it'll look in ${PORTDIR} for checking
# Diego E. Pettenò flamee...@gentoo.org (14 Sep 2009)
# on behalf of QA team
#
# Replaced by app-i18n/skk-jisyo (with cdb USE flag); old
# and stale.
#
# Removal on 2009-11-13
app-i18n/dbskkd-cdb-2
app-i18n/skk-jisyo-cdb
app-i18n/skk-jisyo-extra
# Diego E. Pettenò flamee...@gentoo.org (14 Sep 2009)
# on behalf of QA team
#
# Fails to build for over an year, see bug #233089 opened
# in July 2008.
#
# Removal on 2009-11-13
app-forensics/pyflag
On Sun, 13 Sep 2009 22:17:19 +0200
Sebastian Pipping webmas...@hartwork.org wrote:
Ciaran McCreesh wrote:
Not quite. If both an overlay and the main tree provide foo-1.2,
masking foo-1.2::overlay in Portage would end up masking every
foo-1.2.
Why?
Because an overlay model has only a
Ciaran McCreesh wrote:
Because an overlay model has only a single foo-1.2. Think of it like
stacks of paper. You've got your main repository:
::gentoofoo-1.1 foo-1.2 foo-1.3
and on top of that you put your overlay:
::extras foo-1.2 foo-1.4
::gentoo foo-1.1
On Mon, 14 Sep 2009 20:28:26 +0200
Sebastian Pipping webmas...@hartwork.org wrote:
Ciaran McCreesh wrote:
Because an overlay model has only a single foo-1.2. Think of it like
stacks of paper. You've got your main repository:
::gentoofoo-1.1 foo-1.2 foo-1.3
and on top of that
Sebastian Pipping wrote:
Ciaran McCreesh wrote:
Because an overlay model has only a single foo-1.2. Think of it like
stacks of paper. You've got your main repository:
::gentoofoo-1.1 foo-1.2 foo-1.3
and on top of that you put your overlay:
::extras foo-1.2 foo-1.4
