From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 22:07:32 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9BD0F7AC; Wed, 24 Apr 2013 22:07:32 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 679AA10BF; Wed, 24 Apr 2013 22:07:32 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r3OM7VZE031913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Apr 2013 17:07:31 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Wed, 24 Apr 2013 17:07:31 -0500 From: "Teske, Devin" To: =?Windows-1252?Q?Fernando_Apestegu=EDa?= Subject: Re: GSOC: Qt front-ends Thread-Topic: GSOC: Qt front-ends Thread-Index: AQHOQSB8u/vZWZWEYUqzrBrXPDCeHpjmOC+AgAAJmwA= Date: Wed, 24 Apr 2013 22:07:30 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F1E794@ltcfiswmsgmb21> References: <20130424185452.GA50182@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-04-24_08:2013-04-24,2013-04-24,1970-01-01 signatures=0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Baptiste Daroussin , Devin Teske , Justin Edward Muniz X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 22:07:32 -0000 On Apr 24, 2013, at 2:33 PM, Fernando Apestegu=EDa wrote: El 24/04/2013 21:18, "Teske, Devin" > escribi=F3: > > > On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote: > > > On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote: > >>> > >>> I think the interface to pkgng and freebsd-update are still > >>> interesting; at least more worthwhile than the kernel configuration > >>> one. > >>> > >>> I think the pkgng one has the edge, since packages are updated far > >>> more often than base, and it's easier to track base. > >>> > >>> Now you are at a stage where you should make your own decision; which > >>> one looks the most interesting to you? Once you decide on an area of > >>> interest, you can just start hacking :) > >>> > >>> Chris > >>> > >> > >> > >> That's good to hear. > >> > >> I am sure that you are right, a pkgng GUI would probably see more use = in > >> general. I am definitely close to making my decision, but this thread = has > >> been so much help, I am glad for the insight. > >> > >> The coding is what I look forward to the most :D > > > > imho a pkgng frontend should be done via packagekit, just write a pkgng= backend > > for packagekit and you will gain for FreeBSD a KDE frontend and a GTK f= rontend. > > > > That said any frontend at convenience to contributor will be anyway goo= d :) > > > > If you could pardon my ignorance=85 but what is packagekit again (for the= benefit of others)? It's an application to manage packages. It is developed in a way that it's = easy to add new backends keeping the same interface. See[1] for the general= information and this[2] page for the currently supported back ends. [1] http://www.packagekit.org [2] http://www.packagekit.org/pk-matrix.html Cool. Kinda reminds me of "SANE" for interfacing with scanners. -- Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.