[kde-freebsd] Qt 5.6: Moving .qdocconf files to another port?

[Raphael Kubo da Costa]

Ralf Nolden <nolden at kde.org> writes:

> Am Montag, 18. Juli 2016, 00:02:00 schrieb Raphael Kubo da Costa:
>
>> > The reason is that tcberner and I want to re-work most of the qttools
>> > ports
>> > that are currently split up into several ones to get them merged into as
>> > few ports as possible and reasonable. Then look at the issue of the
>> > qdocconf files again, if we open a bug report on Qt to have these files
>> > moved to qttools as well, which would solve our problem at the source.
>>
>> I don't see how those two issues are related: moving the .qdocconf files
>> to another port, be it a new one or qt5-core, does not prevent the
>> creation of a qt5-tools port that just has to depend on it.
>
> If the global idea is to reduce the number of ports by creating a qt5-tools
> port, it is kinda counter-productive to add a new port for the global qdoc
> files.

[...]

> However, even if using two distfiles may seem as a bad choice, the reason to
> keep things as they are now is that the files belong together. Putting the
> global files into qt5-core seems even more confusing to me than using two
> distfiles to create the port which has everything it needs in itself. The long-
> term goal would be to get rid of that situation but to do that upstream by
> moving the global qdoc files to qttools directly. To me, it just simply got
> forgotten to be moved when the qdoc sources were moved out of qtbase to
> qttools.
>
> Let me check that with upstream if we can fix that somehow.

If upstream moves the .qdocconf files to the qttools tarball, then I
don't have any problems with just putting everything in the qt5-qdoc
tarball in the future.

Until then, I still consider reducing the number of qttools-based ports
and getting rid of the WRKSRC hack independent problems that can be
fixed separately and don't really affect one another.

How about this plan then:
- For Qt 5.6 (and possibly Qt 5.7 since it's already been released), we
  ship a qt5-doc-globalfiles like tcberner suggested and make qt5-qdoc
  depend on it.
- If/when upstream moves the .qdocconf files to qttools, we drop that
  port and put everything back together.