[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[kportage-bugs] [Bug #2563] Not all trees are seen when the portage tre
From: |
nobody |
Subject: |
[kportage-bugs] [Bug #2563] Not all trees are seen when the portage tree is loaded |
Date: |
Sat, 15 Feb 2003 12:09:15 -0500 |
=================== BUG #2563: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2563&group_id=2642
Changes by: Hannes Mehnert <address@hidden>
Date: 2003-Feb-15 17:09 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Resolution | None | Invalid
Status | Open | Closed
------------------ Additional Follow-up Comments ----------------------------
that's the intended behavior. kportage read $PORTDIR/profiles/categories (same
does portage) and looks only in these dirs. kde-apps and kde-libs do not
contain any ebuilds, these are empty directories.
=================== BUG #2563: FULL BUG SNAPSHOT ===================
Submitted by: None Project: KPortage
Submitted on: 2003-Feb-15 16:37
Category: None Severity: 5 - Major
Bug Group: None Resolution: Invalid
Assigned to: None Originator Email: address@hidden
Status: Closed
Summary: Not all trees are seen when the portage tree is loaded
Original Submission: I've noticed that not all of the folders are seen in
kportage that are in the portage tree. For example, kde-apps and kde-libs are
not loaded in kportage. There may be others as well, but i haven't
crossreferenced the folders in /usr/portage with what actually shows up in
kportage.
Follow-up Comments
*******************
-------------------------------------------------------
Date: 2003-Feb-15 17:09 By: hannes
that's the intended behavior. kportage read $PORTDIR/profiles/categories (same
does portage) and looks only in these dirs. kde-apps and kde-libs do not
contain any ebuilds, these are empty directories.
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=2563&group_id=2642