| Summary: | emerge / portage does not use PORTDIR path in message about updating profile. | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Thomas Raschbacher <lordvan> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 456888 | ||
Well portage just echoes whatever the content of the "deprecated" file in the profile happens to be. I suppose we could just replace /usr/portage with your $PORTDIR, but that seems a bit ugly. Maybe it would be a little nicer if we supported variable expansion, so that instances of ${PORTDIR} in deprecated message would expand to whatever the current PORTDIR setting is.
Is it unreasonable to expect that someone using a custom ${PORTDIR} would be smart enough to know how to switch their profile already? That message is just there for the completely clueless.
of course it is reasonable to expect that i'm just pointing out that the message is only correct for default install. alternatively the message could just say something that on default installs it's like that ^_^ Nowadays, people use eselect profile. Latest portage will display the command to run: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=2df35bf46b7fa144272e37d055825f70b46eb0ce |
my PORTDIR is /mnt/space/Portage/tree, but I still get the message below. It really should use ${PORTDIR} instead of hardcoded /usr/portage imho (I'm aware that it isn't recommended for normal users, but it'd be easy to implement I think.) !!! Your current profile is deprecated and not supported anymore. !!! Please upgrade to the following profile if possible: default/linux/x86/2008.0 To upgrade do the following steps: # cd /etc/ # rm make.profile # ln -s ../usr/portage/profiles/default/linux/x86/2008.0 make.profile