summaryrefslogtreecommitdiffstats
path: root/pym/_emerge
Commit message (Collapse)AuthorAgeFilesLines
* Prefer slot conflict over blocker display.Zac Medico2011-10-021-5/+6
| | | | | | | | The slot conflict display has better noise reduction than the unsatisfied blockers display, so skip unsatisfied blockers display if there are slot conflicts (see bug #385391). Note that this reverses the logic from bug 159310, since the slot conflict display has evolved a lot since then.
* print_changelog: if no changelogs, no newlineZac Medico2011-10-021-0/+2
| | | | This will fix bug #385413.
* depgraph: tweak virtual transition codeZac Medico2011-09-301-5/+5
| | | | | | This fixes a false --binpkg-respect-use warning that's triggered by erroneous USE/IUSE comparison between the new-style virtual and an old-style virtual match.
* depgraph: pull in new-style virtuals moreZac Medico2011-09-301-0/+6
| | | | | | | This causes new-style virtuals to get pulled in for virtuals that are already satisfied by installed old-style virtuals. This case is common, due to PROVIDE being (removed without revision bump) from lots of ebuilds.
* tweak "missed updates" code from last commitZac Medico2011-09-281-3/+3
|
* depgraph: verify "missed updates"Zac Medico2011-09-281-0/+4
| | | | | | Since the change involving slot conflict parent atoms in commit 6cea2091526659521d35be6c8dc7733f69f1a760, we want to check to make sure we don't display any false positives in the "missed updates".
* manifest: controllable per repoBrian Harring2011-09-271-9/+12
| | | | | | | | | | | This adds three states to layout.conf key use-manifest; false, true, and strict. false means "don't use manifests at all" true means "use and generate manifests, but allow them to be missing" strict means "manifests must be used everywhere in this repo" BUG=chromium-os:11308 TEST=repoman manifest usage.
* depgraph: handle unicode exception for bug 384749Zac Medico2011-09-271-2/+3
|
* Fix a typo.Arfrever Frehtes Taifersar Arahesis2011-09-231-1/+1
|
* Tweak auto --binpkg-respect-use more.Zac Medico2011-09-221-2/+1
| | | | | | | | We don't want to check for --rebuilt-binaries here, unless --usepkg is also enabled. In fact, we can skip the --rebuilt-binaries check since people who really want to ensure that binary packages are used as much as possible will typically specify --usepkgonly (or --getbinpkgonly which implies --usepkgonly).
* Tweak automatic --binpkg-respect-use behavior.Zac Medico2011-09-213-7/+22
| | | | | | | | If --binpkg-respect-use is not explicitly specified, we enable the behavior automatically (like requested in bug #297549), as long as it doesn't strongly conflict with other options that have been specified. Strongly conflicting options currently include --usepkgonly and --rebuilt-binaries.
* Make --binpkg-respect-use=y the defaultSebastian Luther2011-09-211-4/+6
| | | | | Explicitly stating --binpkg-respect-use=y will disable the ignored binary warning. This will fix bug #297549.
* Warn about ignored binary packages with non matching USESebastian Luther2011-09-211-3/+44
|
* emerge: add --complete-graph-if-new-ver < y | n >Zac Medico2011-09-213-12/+23
| | | | | Trigger the --complete-graph behavior if an installed package version will change (upgrade or downgrade). This option is enabled by default.
* Point users to the man page instead of duplicating it in --helpSebastian Luther2011-09-212-814/+5
|
* autounmask: Always use unresticted atoms for license and USE changesSebastian Luther2011-09-212-17/+12
| | | | See bug 379333.
* Reject inconsistent backtrack parametersSebastian Luther2011-09-202-5/+25
| | | | | | | If backtracking masks a package that caused another package to be masked, we declare this backtracking node as invalid. The backtracker should be able to find another node that gives a valid solution if one exists. This fixes bug 375573.
* Document ** keyword for --autounmask-keep-masks.Zac Medico2011-09-191-2/+2
|
* Suggest --autounmask-keep-masks for ** keyword.Zac Medico2011-09-191-2/+5
|
* Suggest --autounmask-keep-masks instead of --autounmask=nSebastian Luther2011-09-191-7/+3
| | | | | | | Currently emerge suggests --autounmask=n if any configuration change is proposed. With this patch it will print a suggestion only for mask changes, as these are the changes people complain most about. It will suggest --autounmask-keep-masks in this case.
* autounmask: Add --autounmask-keep-masks optionSebastian Luther2011-09-193-1/+21
| | | | | | Disables creation of p.unmask entries to allow users to insist on their masks and hope for another conflict resolution (i.e. missed update). This fixes bug 372485.
* autounmask: Add --autounmask-unrestricted-atoms optionSebastian Luther2011-09-193-16/+48
| | | | | | | | The default behavior of --autounmask is now changed back to the original one, namely to use '=' operators. The --autounmask-unrestricted-atoms option allows the use of '>=' operators whenever possible. This addresses the issues raised in bugs 372405, 374331 and 379333.
* Test --prune with virtual slots.Zac Medico2011-09-181-1/+2
|
* get_dep_chain: fix KeyError if start_node is rootZac Medico2011-09-181-1/+1
|
* autounmask: Document where changes are writenSebastian Luther2011-09-181-1/+5
|
* autounmask: Ensure a suitable parent is displayed in the dep chainSebastian Luther2011-09-181-1/+33
| | | | Fixes bug 375265.
* depclean: don't remove new virtual slotsZac Medico2011-09-181-1/+2
| | | | | | | This provides depclean symmetry with the change in update behavior from commit b95cbb6b78ad6d9b8e2d3edc5fafff122c3ce7c5, so that new virtual slots won't be removed by depclean immediately after they have been pulled in.
* _RepoDisplay: split PORTDIR_OVERLAY with shlexZac Medico2011-09-171-2/+2
| | | | This fixes the issue in bug #383269, comment #8.
* Remove unused Manifest imports.v2.2.0_alpha58Zac Medico2011-09-141-1/+0
|
* Fix multislot handling for depclean (bug #382823)Zac Medico2011-09-141-4/+14
|
* Bind all manifest access through repoconfigsBrian Harring2011-09-122-3/+7
| | | | | This enables controling the behaviour (creation and validation) per repo, and while mildly ugly, refactors in the right direction.
* depgraph: pull in new virtual slots with --updateZac Medico2011-09-111-11/+58
| | | | | | | | This re-implements the fix from commit 21330075f07248765016e104b3ba8216903f1ecb, without introducing the unwanted behavior reported in bug 382557. This involves checking the direct dependencies of virtual slot updates to make sure they are all visible, before pulling them in.
* Revert virtual slot update code for bug 382557.Zac Medico2011-09-111-1/+0
| | | | | | This reverts the behavior change from commit 21330075f07248765016e104b3ba8216903f1ecb, since it's too aggressive in pulling in new virtual slots that may have masked dependencies.
* depgraph: refactor virtual slot --update codeZac Medico2011-09-101-28/+26
| | | | | | | This re-implements the change from commit 21330075f07248765016e104b3ba8216903f1ecb in order to avoid executing unnessary virtual slot expansion code when the given atom specifies a slot or --update is enabled.
* depgraph: use Atom.with_slot() to match virtualsZac Medico2011-09-101-1/+1
| | | | This ensures that USE deps and repo deps are preserved here.
* depgraph: use _iter_match_pkgs_any where possibleZac Medico2011-09-091-6/+5
|
* depgraph: pull in new virtual slots with --updateZac Medico2011-09-091-1/+7
| | | | | | | | Previously, the virtual cost minimization code from bug #141118 would prevent virtual dependencies from pulling in new slots. That behavior was not desired for --update, so now it's fixed to pull in the latest slot available. This allows virtual/jdk-1.7.0 to be pulled in by dependencies when --update is enabled.
* Update unread news items in --pretend mode.Zac Medico2011-09-041-4/+17
| | | | | | | | | This has been disabled since commit c7faa634369e61b87a40172ceb0a5cb9494fd518, but the only reason cited was to avoid permissions issues. So, go ahead and enable it, and handle PermissionDenied just in case. NOTE: The NewsManager typically handles permission errors by returning silently, so PermissionDenied won't necessarily be raised even if we do trigger a permission error.
* Join /var/log/emerge.log with EPREFIX.Zac Medico2011-09-031-1/+10
|
* Handle unpickle EOFError.Zac Medico2011-09-031-1/+1
|
* Handle unpickle AttributeError (bug #381705).Zac Medico2011-09-031-3/+7
|
* Show merge list before "missed update" messages.Zac Medico2011-09-011-0/+2
|
* Add FEATURES=clean-logs support.Zac Medico2011-08-311-2/+33
| | | | | | | Enable automatic execution of the command specified by the PORT_LOGDIR_CLEAN variable. The default PORT_LOGDIR_CLEAN setting will remove all files from PORT_LOGDIR that were last modified at least 7 days ago.
* Respect package.env buildpkg FEATURES settings.Zac Medico2011-08-303-4/+9
| | | | This will fix bug #318897.
* Send "Recording in world" msg to stdout.Zac Medico2011-08-281-1/+2
|
* Fix "ResourceWarning: unclosed file" with Python 3.2.Arfrever Frehtes Taifersar Arahesis2011-08-271-1/+1
|
* python3.2 fixes: ResourceWarning: unclosed fileZac Medico2011-08-261-1/+1
|
* Update --rebuild-if-* flags to rebuild when build dependencies are changed.David James2011-08-262-99/+69
| | | | | | | | | | | | | | Right now, the --rebuild-if-* flags only rebuild packages that are used at both run-time and build-time. This doesn't help for packages that are used only at build-time (for example, static libaries). Rebuilding packages whenever a build-time dependency is changed is easier to understand and explain, and it handles all cases correctly. BUG=chromium-os:15517 TEST=Run emerge test suite. Change-Id: Iae8dab24e8acb6625bc1a0ce41862e90b232eb84
* python3.2 fixes: ResourceWarning: unclosed fileZac Medico2011-08-261-1/+2
|
* python3.2 fixes: ResourceWarning: unclosed fileZac Medico2011-08-251-0/+13
|
generated by cgit v1.2.3-1-g7c22 (git 2.25.1) at 2024-06-28 21:58:07 +0000