Qt 5 private headers

[Ruslan Nigmatullin]

Great,

Sure, I'll leave comments there once would achieve some progress.

19.06.2015, 07:21, "Rex Dieter" <rdieter at math.unl.edu>:
> Rex Dieter wrote:
>
>>  Rex Dieter wrote:
>>
>>>  Ruslan Nigmatullin wrote:
>>>
>>>>  12.06.2015, 16:32, "Rex Dieter" <rdieter at math.unl.edu>:
>>>>>  Ruslan Nigmatullin wrote:
>>>>>
>>>>>>>  Are you willing to help work on it? :)
>>>>>>
>>>>>>  Sure, I may have a look. How can I start?
>>>>>
>>>>>  Start by identifying precisely what should be declared as private.
>>>>>  Offhand I see:
>>>>>  /usr/include/qt5/*/private/
>>>>>  /usr/lib(64)/qt5/mkspecs/modules/qt_lib*_private.pri
>>>>>
>>>>>  anything more than that?
>>>>
>>>>  Sorry for misunderstanding, my question is about more final step, what
>>>>  should I do once I get modified *.spec file and check it by rpmbuild?
>>>>  Should I send it to one of current Qt5 maintainers?
>>>
>>>  Let's take baby steps, starting with the first. identifying the content
>>>  that should be declared as private.
>>>
>>>  fyi, I'm one of the Qt5 maintainers, so you're talking to the right
>>>  people already.
>>
>>  A colleague pointed out the debian is already doing -private splits too,
>>  for example,
>>
>>  https://packages.debian.org/sid/i386/qtbase5-private-dev/filelist
>>
>>  which is close to what I expected (minus the
>>  mkspecs/modules/qt_lib*_private.pri though)
>
> FYI, I opened a bug to track the progress of implementing this feature,
> https://bugzilla.redhat.com/show_bug.cgi?id=1233829
> aka
> https://bugzilla.redhat.com/show_bug.cgi?id=qt5-private
>
> Feel free to add technical details there.
>
> -- Rex
>
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

--
Ruslan Nigmatullin