Created attachment 162817 [details]
Created attachment 162818 [details]
Summary of changes:
* Removed wxWidgets because wxWidgets are completely removed from the project (as per ChangeLog)
* Added NLS option due to gettext use
I ran poudriere build with and without QT5, both work. QT5=off is default.
I would prefer to enable QT% option by default, considering it is the only GUI now.
But most people will use it as a command line utility. Enabling QT by default would pull a ton of dependencies for just one simple window.
(In reply to yuri from comment #3)
> But most people will use it as a command line utility. Enabling QT by
> default would pull a ton of dependencies for just one simple window.
Firstly GUI option (WXGTK) was enabled by default before the project has switched to different toolkit. Secondly, for users which primarily use packages building the port without GUI option (if they don't want to install Qt 5) is less problematic than vice versa.
Btw, the NLS option is not respected. Would you like to spend more time on it? Alternatively I could revert it.
Ok, thanks, I will fix it.
Created attachment 162890 [details]
* set QT5=on as a default
* fixed NLS option
poudriere build still passes.
A commit references this bug:
Date: Wed Nov 18 10:47:27 UTC 2015
New revision: 401860
- Update to 8.5.2.
- WXGTK support has been removed upstream in favour of Qt
- Amend BROKEN message
- Enable verbose build when PACKAGE_BUILDING is set (instead of BATCH)
- Decouple CURL option for online update checks from QT5
- Add NLS option
- Sort plist
PR: based on 204312
Submitted by: email@example.com
Thanks, I've committed slightly modified version. For the future, you don't have to supply poudriere build log along with a patch. If committer reveals a problem during testing, then the attached build log proves nothing, and if the patch is ok, then the build log is not needed.
Well, people were asking for poudriere build before.
(In reply to yuri from comment #9)
> Well, people were asking for poudriere build before.
It's a committer responsibility to properly check submitted patch. Of course this doesn't mean submitters shouldn't test it. Instead of providing build logs you could tell which OS versions/architectures the patch has been tested with poudriere.