suggestions: (1) add --get-base-path ... would return /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/ in the case of 3.2.1 ... i know OOo *needs* this to build, there might be other apps that would utilize it (2) remove a lot of the enters in the --help screen ... turn [--get-lib-path] Print path where libraries of given/current profile are located. [--get-stdcxx-incdir] Print path to g++ include files of given/current profile. into [--get-lib-path] Print path where libraries of given/current profile are located. [--get-stdcxx-incdir] Print path to g++ include files of given/current profile. personally i hate having to scroll console just to see all the help :p
2 more suggestions ... it would be nice to have short options ... i hate typing in long options all the time when running `gcc-config --list-profiles` add the ability to select profiles with a single # (easier to switch profiles when testing ebuild compiles on diff gcc versions) so you would go from this: root@vapier portage # gcc-config --list-profiles i686-pc-linux-gnu-2.95.3 i686-pc-linux-gnu-3.2.1 root@vapier portage # gcc-config i686-pc-linux-gnu-3.2.1 * Switching to i686-pc-linux-gnu-3.2.1 compiler... [ ok ] to this: root@vapier portage # gcc-config --list-profiles [1] i686-pc-linux-gnu-2.95.3 [2] i686-pc-linux-gnu-3.2.1 root@vapier portage # gcc-config 2 * Switching to i686-pc-linux-gnu-3.2.1 compiler... [ ok ]
1) I do not see the point. Your base path is also the lib path ... Why have two options for the same thing ? 2) Sure, it do look neater =)
Blah, links is braindead. Comment #2 are no priority. If I ever get to it\n I will do it. Commited changes to cvs for comment #1 point 2).
Been there, done that, in gcc-config-1.3.3 ;)
