The new portage has just gone out. I see that -U is 'deprecated' with an obscure message about /etc/portage. The manpage for 'emerge' is for 2.0.48 and is irrelevant. Documentation must be available!! Reproducible: Always Steps to Reproduce: 1. 2. 3.
just because we dont change the version numbers in the manpage doesnt mean the manpages arent updated
I should have been more explicit. The man page for emerge 2.0.51_rc1 Does contain irrelevant information and deprecated features. Does not contain information on new features. The man pages have not be updated in this instance.
you really werent more specific ... what 'irrelevant information' does it contain ? (even if it is deprecated the documentation will stay in there until we actually remove it) what 'new features' are missing ?
Ok, The -U flag This option is deprecated and shouldn't be used anymore. Please use the /etc/portage/package.* files from now on. There is no information in the man page about the /etc/portage tree or how to use it. Ebuilds ebuild An ebuild must be, at a minimum, a valid Portage package direc- tory name without a version or category, such as portage or python. Both categories and version numbers may be used in addition, such as sys-apps/portage or =python-2.2.1-r2. emerge ignores a trailing slash so that filename completion can be used. The ebuild may also be an actual filename, such as /usr/portage/app-admin/python/python-2.2.1-r2.ebuild. Try it and... !!! Warning: emerge /path/to/ebuild is broken and considered dangerous. !!! Don't use it. I'm serious, we're coming after you if you use it. The /var/lib/portage tree is not documented and /var/cache/edb is,
-U flag still exists hence it'll stay you havent read the portage(5) manpage the `emerge /path/to/ebuild` is semi-broken hence the warning i already updated /var/lib/portage in the portage(5) manpage all in all i dont see anything here that hasnt been handled already ...
