From owner-freebsd-ports@freebsd.org Mon Dec 24 10:52:04 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 577B2133E997 for ; Mon, 24 Dec 2018 10:52:04 +0000 (UTC) (envelope-from phascolarctos@protonmail.ch) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E74AD8193E for ; Mon, 24 Dec 2018 10:52:03 +0000 (UTC) (envelope-from phascolarctos@protonmail.ch) Date: Mon, 24 Dec 2018 10:51:54 +0000 To: FreeBSD Ports From: Lorenzo Salvadore Reply-To: Lorenzo Salvadore Subject: Re: category qt? Message-ID: In-Reply-To: References: Feedback-ID: X6az_D2smWSR8MT5MHqXnWF0upxehDyHia7Id1cbayHNBUkRu3CIeusDsZHiivIIjmaKB1_OofpALrRUYjNz3w==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch X-Rspamd-Queue-Id: E74AD8193E X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.985,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2018 10:52:04 -0000 > The qt* ports spreads around in the whole portstree. > > It is reasonable to concentrate all these ports in a qt category? I > think it is easier to find (and also easier to maintain). Indeed it is a bit annoying for me when I have to update qt* ports. I don't use portmaster or similar (I don't like them): I wrote my own utility, but it has still some issues, such as this one. I guess having all the qt* ports in the same category would help. Lorenzo Salvadore.