| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
svn path=/main/trunk/; revision=9616
|
|
|
|
| |
svn path=/main/trunk/; revision=9615
|
|
|
|
| |
svn path=/main/trunk/; revision=9613
|
|
|
|
|
|
|
| |
down into dep_check() for better atom preference selection when handling
virtuals and other disjunctive || dependencies. (branches/2.1.2 r9610)
svn path=/main/trunk/; revision=9611
|
|
|
|
|
|
| |
like StaticFileSet and won't pull in lower slots.
svn path=/main/trunk/; revision=9607
|
|
|
|
|
|
| |
automatically delete it.
svn path=/main/trunk/; revision=9589
|
|
|
|
|
|
|
| |
the merge list where it is most likely to be seen (along with other depgraph
problems).
svn path=/main/trunk/; revision=9584
|
|
|
|
|
|
| |
no point in examining any lower versions from the same repo.
svn path=/main/trunk/; revision=9514
|
|
|
|
| |
svn path=/main/trunk/; revision=9513
|
|
|
|
| |
svn path=/main/trunk/; revision=9496
|
|
|
|
|
|
| |
match before rejecting other available packages.
svn path=/main/trunk/; revision=9495
|
|
|
|
| |
svn path=/main/trunk/; revision=9488
|
|
|
|
|
|
|
| |
are respected. Also, eliminate duplicate package selections since the same
package may be selected by multiple atoms but we can only unmerge it once.
svn path=/main/trunk/; revision=9483
|
|
|
|
|
|
| |
`repoman manifest` is the preferred way to generate manifests.
svn path=/main/trunk/; revision=9482
|
|
|
|
| |
svn path=/main/trunk/; revision=9480
|
|
|
|
| |
svn path=/main/trunk/; revision=9478
|
|
|
|
|
|
| |
is matched by multiple atoms
svn path=/main/trunk/; revision=9477
|
|
|
|
| |
svn path=/main/trunk/; revision=9473
|
|
|
|
|
|
| |
* Add parallel-fetch to the default FEATURES since it is more efficient now.
svn path=/main/trunk/; revision=9462
|
|
|
|
|
|
|
| |
the package does not need to be reinstalled and the installed version is not
masked.
svn path=/main/trunk/; revision=9457
|
|
|
|
|
|
| |
asked to remove specific packages since it's relatively safe in this case.
svn path=/main/trunk/; revision=9451
|
|
|
|
| |
svn path=/main/trunk/; revision=9409
|
|
|
|
| |
svn path=/main/trunk/; revision=9395
|
|
|
|
| |
svn path=/main/trunk/; revision=9394
|
|
|
|
|
|
|
|
| |
config["PORTAGE_USE"] (which is filtered for intersection with IUSE)
so that dependency calculations at installation time are consistent
with those at depclean time.
svn path=/main/trunk/; revision=9392
|
|
|
|
|
|
| |
up USE calculations for world updates.
svn path=/main/trunk/; revision=9391
|
|
|
|
| |
svn path=/main/trunk/; revision=9388
|
|
|
|
|
|
|
|
| |
config["PORTAGE_USE"] (which is filtered for intersection with IUSE)
so that dependency calculations at installation time are consistent
with those at depclean time.
svn path=/main/trunk/; revision=9387
|
|
|
|
|
|
| |
package then just unmerge them alphabetically.
svn path=/main/trunk/; revision=9385
|
|
|
|
|
|
|
|
| |
with / and it's not recognized as a tbz2 or ebuild then we try to find
and owner in the vdb and generate a slot atom from it. Thanks to solar
for the suggestion.
svn path=/main/trunk/; revision=9367
|
|
|
|
|
|
| |
the graph so there's less noise.
svn path=/main/trunk/; revision=9362
|
|
|
|
| |
svn path=/main/trunk/; revision=9360
|
|
|
|
|
|
| |
instead of the old portdbapi hack.
svn path=/main/trunk/; revision=9350
|
|
|
|
|
|
| |
a dict to a list.
svn path=/main/trunk/; revision=9349
|
|
|
|
|
|
|
|
|
| |
slots of the same package are being unmerged then they are not necessarily
unmerged consecutively. To make the display less confusing, never display
packages as "protected" or "omitted" when they actually belong to the
overall set of "selected" packages to be unmerged.
svn path=/main/trunk/; revision=9348
|
|
|
|
|
|
| |
even when they don't have any dependencies.
svn path=/main/trunk/; revision=9347
|
|
|
|
|
|
| |
given to it by the user or depclean.
svn path=/main/trunk/; revision=9346
|
|
|
|
|
|
| |
graph if they are being removed.
svn path=/main/trunk/; revision=9345
|
|
|
|
| |
svn path=/main/trunk/; revision=9343
|
|
|
|
|
|
| |
shouldn't be cleaned.
svn path=/main/trunk/; revision=9341
|
|
|
|
| |
svn path=/main/trunk/; revision=9340
|
|
|
|
|
|
|
|
| |
each package is unmerged before it's dependencies. This is necessary to
avoid breaking things that may need to run during pkg_prerm or pkg_postrm
phases.
svn path=/main/trunk/; revision=9339
|
|
|
|
|
|
| |
currently supported priorities and categories.
svn path=/main/trunk/; revision=9338
|
|
|
|
| |
svn path=/main/trunk/; revision=9337
|
|
|
|
|
|
|
|
|
|
|
|
| |
when selective is True and the currently installed version does
not have a matching ebuild in the tree. For example, this type of
situation is likely to occur if the user somehow obtains a binary
package that has a newer version than any of the ebuilds in the
portage tree. If package maintainers want to encourage a downgrade
in a case like this then they should use package.mask so that the
user receives a warning about the installed package being masked.
svn path=/main/trunk/; revision=9336
|
|
|
|
|
|
| |
shows the "Unknown (missing digest)" message instead of a traceback.
svn path=/main/trunk/; revision=9333
|
|
|
|
|
|
|
| |
packages. We can assume that if the user accepted the keywords at merge
time then they never want to be bothered again.
svn path=/main/trunk/; revision=9330
|
|
|
|
|
|
| |
between visible() and get_masking_status().
svn path=/main/trunk/; revision=9324
|
|
|
|
|
|
|
| |
return 1 when PORTAGE_RSYNC_RETRIES is exceeded.
svn path=/main/trunk/; revision=9321
|
|
|
|
|
|
|
| |
out of date it's not interpreted like an actual rsync exitcode
(to avoid a misleading exitcode interpretation message).
svn path=/main/trunk/; revision=9320
|