This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] honor program_transform_name on installation of info manuals


Geoff Keating writes:
> Gerald Pfeifer <gerald@pfeifer.com> writes:
> 
> > On Wed, 18 Feb 2004, Geoff Keating wrote:
> > >> it's my understanding that the --program-suffix option should allow
> > >> parallel installation of more than one GCC version with the same path
> > >> prefix.
> > > I've heard that, but I have no evidence that it's true.  The only
> > > documentation of --program-* seems to be in the configure --help:
> > >
> > >    --program-prefix=PREFIX prepend PREFIX to installed program names
> > >    --program-suffix=SUFFIX append SUFFIX to installed program names
> > >    --program-transform-name=PROGRAM
> > >                            run sed PROGRAM on installed program names
> > >
> > > Info files aren't named based on a program name...
> > 
> > Well, but with GCC we are currently shipping the following info files,
> > in addition to gcc.info:
> > 
> >   cpp.info
> >   cppinternals.info
> >   g77.info
> >   gccinstall.info
> >   gccint.info
> >   gcj.info
> >   fastjar.info
> > 
> > I suppose this is one of those cases, where the GNU documentation simply
> > is not explicit to the last detail.
> > 
> > And there are at least two major distributions I am aware of, namely
> > Debian and FreeBSD, who would like to use this feature.
> 
> Sure.  As I said, I'm not sure either way.
> 
> Whatever we do, it should certainly be documented.
> 
> > >>  what would you propose to achieve this installation option?
> > > What do other GNU programs do?
> > 
> > I guess there are very few other GNU programs where one often needs to
> > have different versions installed. :-}
> 
> autoconf?  automake?  make?  bison?  emacs?
> 
> I know that Red Hat FC1 has at least 3 versions of automake installed.
> 
> In fact, automake should be a very good example, since it pretty much
> sets the standard for GNU programs.  I think that whatever we do
> should be the same as automake does; if we don't want that, automake
> should be changed first.

please don't make a chicken-egg problem. checked the various automake
packages in Debian. The renaming/rebuilding/patching is done in the
packaging, not in the upstream sources.

an alternative might be to install the unchanged info files in a
subdirectory and use something like 'GCC-3-5' as the menu name and
'3.5/gcc' as the info file name. however the cross document references
in the info files need to be changed for this alternative as well.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]