Hi! I tested the port on amd64:
- The build is fine - Installed the -nox package - Started downloading a torrent - Installed the main package on top of that, no errors. - The download has been finished properly. - Deinstalling caused no issues as well. I met the same segfaults at exit that Elias mentioned earlier with the Qt interface, but it doesn't affect the stability of the program itself. As a user, it's fine for me. Charlène. On Fri, 31 Aug 2018 16:44:35 -0300 Elias M. Mariani wrote: > Sorry for pinging, > Just a small change to the README of qbittorrent-nox, tweak from > Charlene Wendling. > > Cheers. > Elias. > > 2018-08-28 16:34 GMT-03:00 Elias M. Mariani <marianiel...@gmail.com>: > > Separate ports sharing the same parent folder (net/qbittorrent) it > > is then. > > > > > > 2018-08-27 20:04 GMT-03:00 Stuart Henderson <s...@spacehopper.org>: > >> On 2018/08/27 19:30, Elias M. Mariani wrote: > >>> Yes, but in this case they are built separately and the do not > >>> share any files. > >>> > >>> Cheers. > >>> Elias. > >>> > >>> 2018-08-27 18:14 GMT-03:00 Stuart Henderson <s...@spacehopper.org>: > >>> > On 2018/08/27 15:17, Elias M. Mariani wrote: > >>> >> Also if someone could check if I'm using correctly the FLAVORS. > >>> >> The port creates 2 packages that are built separately: > >>> >> - qbittorrent (Qt5 + web interface) > >>> >> - qbittorrent-nox (web interface only) > >>> >> My doubts come when using the PLIST when all the files are > >>> >> different. (I think that is OK but getting feedback doesn't > >>> >> hurt...) > >>> > > >>> > That would usually be done a single build (i.e. get rid of the > >>> > flavour, split it in the packaging stage instead using > >>> > MULTI_PACKAGES and PLIST-main and PLIST-nox). > >>> > > >>> > >> > >> Multiple flavours are for when you build mostly the same files with > >> different options. You can skip some files for certain flavours, > >> but when there is no overlap at all, that is not the situation > >> flavours are meant to deal with. > >> > >> Can you get both of them to build in a single run? If so, > >> MULTI_PACKAGES. If not, separate ports (can share a parent > >> directory and some scaffolding via Makefile.inc). > >>