Summary: | emerge --update --pretend rsync -> error | ||
---|---|---|---|
Product: | Portage Development | Reporter: | nachtklavier <nachtklavier> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | gurligebis |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
nachtklavier
2003-12-04 01:54:43 UTC
The whole "rsync" to "sync" mapping should be IMHO dropped... Radek I think the command should be changed to something like portage-update , so the emerge command shouldn't be used for that. mmh, reading the second comment, i'm not sure if i understand it correctly. i just want to see what happens when i'm updating the package "rsync"... so i think emerge gets confused by whatever and thinks i want to sync something. yep, that is also what i mean. But then what if there is added a package called sync, then that one wouldn't work any longer. That is why I surgest that the emerge command should not be used for updating the portage tree. |