summaryrefslogtreecommitdiffstats
path: root/pym/portage/package/ebuild/_config/KeywordsManager.py
Commit message (Collapse)AuthorAgeFilesLines
* isStable: fix * logic for repomanZac Medico2013-01-191-1/+5
|
* isStable: handle * for repoman moreZac Medico2013-01-191-1/+1
|
* isStable: handle * for repomanv2.2.0_alpha156Zac Medico2013-01-191-1/+1
|
* Fix stable mask logic for repoman.Zac Medico2013-01-191-9/+19
| | | | | | For repoman, if the package has an effective stable keyword that intersects with the effective ACCEPT_KEYWORDS for the current profile, then consider it stable.
* KeywordsManager: fix isStable commentZac Medico2012-08-251-1/+1
|
* EAPI 5 stable use.mask/force for bug #431078Zac Medico2012-08-241-0/+27
|
* _pkg_str: pass in config + metadata with KEYWORDSZac Medico2012-08-241-6/+9
| | | | | This will be needed in order to support stable use.mask/force for bug #431078.
* _pkg_str: add slot and repo attributesZac Medico2012-05-121-10/+11
|
* LocationsManager: extensible _profile_node objectZac Medico2011-10-271-2/+4
| | | | Use immutable object attrubutes instead of tuples, for extensibility.
* add profile-formats portage-1 awareness and enforcementBrian Harring2011-10-251-2/+2
| | | | | | | | Currently it just spits warnings for implicit portage-1 format usage; down the line, this will be converted into an explicit error. For repo's that configure themselves as portage-1 or pms explicitly, enforce it.
* KeywordsManager: support ~* in KEYWORDSZac Medico2011-10-011-6/+10
| | | | | | | | | | | | This allows ~* in KEYWORDS to be match by any unstable keyword in the user's configuration, similar to how * in KEYWORDS already matches any user configuration. Thanks to Daniel Robbins <drobbins@funtoo.org> for the suggestion. Also, the warning about * or -* in KEYWORDS is now gone, so that ebuilds from the funtoo tree will be usable without triggering warnings like this. If necessary, we can add ways to selectively enable these kinds of warnings via layout.conf and/or repos.conf.
* Use Package.UNKNOWN_REPO where appropriate.Zac Medico2011-06-061-1/+2
|
* Display: Simplify mask code for bug #58416.Zac Medico2011-01-311-19/+4
| | | | | | Hopefully this makes the logic more understandable, though it may support fewer cases. If we want to handle more cases then hopefully we can do it without making the code too complex.
* getRawMissingKeywords: fix getEgroups breakageZac Medico2011-01-311-1/+1
|
* KeywordsManager: use lists where order mattersZac Medico2011-01-301-11/+12
| | | | | | Also remove x.lstrip('~') code from from getRawMissingKeywords() since I don't understand it (was only recently added, and we can add back later if appropriate).
* Properly fix my earlier breakageBrian Dolbec2011-01-301-38/+21
|
* Fix keywords breakage from last 2 commits.Zac Medico2011-01-301-1/+15
|
* split up the getMissingKeywords code to eliminate code duplication and ↵Brian Dolbec2011-01-301-94/+130
| | | | increase flexibility. Do some pyflakes and pylint cleanup
* add getRawMissingKeywords functionsBrian Dolbec2011-01-301-1/+81
|
* Remove a part of a comment, which is about files not handled in ↵Arfrever Frehtes Taifersar Arahesis2010-11-061-5/+1
| | | | KeywordsManager.py.
* reposyntax: add support in _config/*Sebastian Luther2010-09-261-8/+10
|
* Fix some typos.Arfrever Frehtes Taifersar Arahesis2010-09-141-3/+3
|
* In KeywordsManager.pkeywordsdict save values as tuples instead of lists.Zac Medico2010-09-141-0/+2
|
* config: Add KeywordsManagerSebastian Luther2010-09-141-0/+184