Bug#460015: gfortran-doc: could be updated to depend on gfortran-4.2-doc

[Matthias Klose <doko@cs.tu-berlin.de>]

> > > Since this is related to "gcc-dco-non-dfsg" infrastructure, I think
> > > this should be postponed until "FDL docs in gcc" is resolved. Which
> > > will probably happen only when gcc-4.3 enters unstable.
> >
> > Do you mean to imply that gcc 4.3 documentation will be licensed under
> > something other than GFDL?  If so, that's great news!  Would you happen
> > to have a link to somewhere I can read more about this?
> 
> No, I don't believe that GCC documentation license will change.
> 
> Overall situation is the following.
> 
> Short before etch release, GFDL docs have been considered non-free and=20
> removed from main. So it very looked like etch will be released without=20
> gcc documentation at all. I did not like it, and created gcc-4.1-=20
> doc-non-dfsg [non-free] and gcc-doc-defaults [contrib] packages that=20
> provided documentation.
> 
> After etch release, gcc packages started to build documentation again.=20
> 
> =46YI:
> 
> > > > > Currently, gcc-4.2-doc *is* in main. Does this mean that FDL
> > > > > paranoia has gone to past, or gcc-4.2-doc is in main just in error
> > > > > - I don't know. But depending on this, either non-free and contrib
> > > > > packages should be updated, or gcc-doc should be provided by
> > > > > gcc-defaults (as it was some time ago).
> > > > >
> > > > > Matthias, could you please comment on this?
> > > >
> > > > please see my comment in #442445
> > >
> > > from #442445:
> > > > won't fix this before the 4.2.3 and 4.3.0 releases
> > >
> > > Not very verbose :)
> > >
> > > Could you please answer what is going to be changed at the time of
> > > 4.2.3/4.3.0?
> >
> > the man pages and -doc packages won't be built anymore with the final
> > 4.2.3/4.3.0 releases.
> >
> > > Will you handle documentation issues yourself?
> >
> > I won't touch the non-free -doc packages.
> >
> > > Or my non-free/contrib packages are will be needed again?
> >
> > most likely.
> 
> So unless Matthias changes his mind, I think the best strategy is to update=
> =20
> documentation packages when "final 4.2.3/4.3.0 releases" will be uploaded,=
> =20
> and not bother until then.

yes, the final 4.2.3/4.3.0 packages won't include the documentation;
having to remove the files from each snapshot is just bogus work.

  Matthias