Date: Mon, 28 May 2018 13:35:41 -0600 From: Sean Bruno <sbruno@freebsd.org> To: yuri@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r471061 - head/audio/qjackctl Message-ID: <d42ac45a-2357-630a-8a0d-6864f271d4a9@freebsd.org> In-Reply-To: <77503afc-b631-ac32-a87b-c8a28e0bb2ab@freebsd.org> References: <201805281845.w4SIj8bO065379@repo.freebsd.org> <985846ee-dce7-d8f1-2813-0a28bc36217e@freebsd.org> <a328123e-8f85-6d68-1d9d-b7454b53fe25@freebsd.org> <5dddd567-3439-caa3-56d0-665a40bdbf35@freebsd.org> <77503afc-b631-ac32-a87b-c8a28e0bb2ab@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --a47mlyj6kGbKKIiKI9RtuJVJhjkGevpD2 Content-Type: multipart/mixed; boundary="DUA3qBmshLybjW8KpGCcSVph8aCY6v2JS"; protected-headers="v1" From: Sean Bruno <sbruno@freebsd.org> To: yuri@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Message-ID: <d42ac45a-2357-630a-8a0d-6864f271d4a9@freebsd.org> Subject: Re: svn commit: r471061 - head/audio/qjackctl References: <201805281845.w4SIj8bO065379@repo.freebsd.org> <985846ee-dce7-d8f1-2813-0a28bc36217e@freebsd.org> <a328123e-8f85-6d68-1d9d-b7454b53fe25@freebsd.org> <5dddd567-3439-caa3-56d0-665a40bdbf35@freebsd.org> <77503afc-b631-ac32-a87b-c8a28e0bb2ab@freebsd.org> In-Reply-To: <77503afc-b631-ac32-a87b-c8a28e0bb2ab@freebsd.org> --DUA3qBmshLybjW8KpGCcSVph8aCY6v2JS Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/28/18 13:11, Yuri wrote: > On 05/28/18 12:02, Sean Bruno wrote: >> The problem I am describing is that *if* I am using applications that >> are QT4 only, this change now forces me too build QT5 to get this one >> port built. >> >> Maybe its better to leave QT4 in place but make QT5 the default? >=20 >=20 > I made such changes before (deprecate Qt4) elsewhere and nobody complai= ned. I didn't know I was complaining. I thought I was asking about a change you made and trying to engage in a civil conversation about it. >=20 > It's like if some package is updated from mypkg-4.0 to mypkg-5.0, the > port changes to mypkg-5.0, and the users have to update. The ports > system doesn't provide a way to stay with mypkg-4.0. Why Qt should be > different? It has to deprecate Qt4 at some point. Qt4 hasn't been shown= > to provide any benefit, generally. >=20 >=20 This happens quite a lot actually. I don't find this argument valid. Is there information from Portmgr or the team that maintains/works on QT saying that QT4 is going to be deprecated? I couldn't find one if it exists. > If some app doesn't support Qt4, you should complain to that app, IMO. > Your situation sounds like a fringe case that most users don't care abo= ut. >=20 >=20 But, this app DOES support QT4. Until this change was made, it ran and built just fine. It also builds and runs just fine with QT5, so I don't have any objection to the default of QT5. Defaulting to QT5 seems very sensible to me. sean --DUA3qBmshLybjW8KpGCcSVph8aCY6v2JS-- --a47mlyj6kGbKKIiKI9RtuJVJhjkGevpD2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlsMWg1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LY4jwgAi4xK+mIYKnegH2u7K/brh7rPZcqjBMljMZZgtQ6dfivvdGsljJKaamf5 1qPeK813MnbRiSPxjjkYmkubnNyD2oZqDXWS0J50XPOtxMsg3lYM+TPQzKf9tI4N NgL+Key9tL3abLNzCVJrQnv++6b8HclD99giDEa9Drq3GR9F+Fq9Q9RmtA/EtFQg qrEBIq2w5PBwiGMyXZlzNgWyO+CkU/i4FBN3Rw5Egy6Wrad87t2hjxtKgVAsOC8a Dnq3X7JfoMqnjncBls3sAm0fFlsgsh56zoYl7Wy8TOGAie6zKAdVSUtJZQEK1Ix1 bamPxUCHWDvoNWv7o+U4bQHJxNw7dw== =+HMY -----END PGP SIGNATURE----- --a47mlyj6kGbKKIiKI9RtuJVJhjkGevpD2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d42ac45a-2357-630a-8a0d-6864f271d4a9>