From owner-freebsd-current@FreeBSD.ORG Sat Mar 7 03:28:01 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A14281D for ; Sat, 7 Mar 2015 03:28:01 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96894EC9 for ; Sat, 7 Mar 2015 03:28:00 +0000 (UTC) Received: by lbiw7 with SMTP id w7so14528232lbi.6 for ; Fri, 06 Mar 2015 19:27:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ejGIXEzWPmv/3CO3gfGMhTb7rbq8elnwMwQj7hkTUUk=; b=SuQG2uWxEt44O7obMnW3AaU2dkDh/M0HE9J4KbuRBzUlSACP5v/Uj0BWA5w9pP+YQU sk2Kkvn4tYrrxfxrU+Ef1M4AGqWK/faqH4u9lE8+sVtZy+LxoUZLuL68bKj2KoXt/Hi9 Lnak4ZEYKwG+bax1R9G2QfyF/USSsqlIbGjwpvUZQixa2uvuyeA3DZmUAVm8XY/BXgxs bhMkH2HRXMe89DjtRoJ7DwyTBU22qxaol7+AEyWaDGOVa/R6DpTWHYW2Lh/BMg7v9Qea LkvSCFayFQi2maNpeJnw6boUucq4e2SYhyB3W82ZZL0VE1HNJPn8w2UO8z27PpF/V/+I UyYg== MIME-Version: 1.0 X-Received: by 10.112.26.209 with SMTP id n17mr10655817lbg.84.1425698878472; Fri, 06 Mar 2015 19:27:58 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.82.164 with HTTP; Fri, 6 Mar 2015 19:27:58 -0800 (PST) In-Reply-To: References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <54F35F29.4000603@astrodoggroup.com> <54F429EF.5050400@freebsd.org> <54F46536.8040607@mu.org> <54F4C03F.7030704@freebsd.org> <54F4FECB.90501@freebsd.org> <197AA5DC-0591-4F71-BF10-51A5D8104C11@mu.org> <54F5270D.1010009@freebsd.org> Date: Fri, 6 Mar 2015 19:27:58 -0800 X-Google-Sender-Auth: GyhVI8tJNq1dhXzZzZvIhJXI78o Message-ID: Subject: Re: Massive libxo-zation that breaks everything From: Craig Rodrigues To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Mar 2015 03:28:01 -0000 On Mon, Mar 2, 2015 at 7:33 PM, Alfred Perlstein wrote: > > > Actually I want to shame third party ports into adopting libxo (or at least providing machine readable output). Well if upstream third party ports adopt libxo will remain to be seen. However, one thing we can do is to make it super-duper easy for them to incorporate. Then it will be a no-brainer for them to use libxo. I would like to see a Debian package of libxo made, so it can be incorporated into Debian and Ubuntu derived Linux distributions. I have done similar Debian packaging efforts for kyua, atf, and lutok: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773277 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773278 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773279 Does anyone have connections in the Debian community to push these kinds of reviews forward? I've asked on the debian-bsd mailing list, but got no help. I basically need a "Debian Developer" who has privileges to upload packages to the Debian distribution to take the packages that I have made and upload them (after making sure they pass lintian checks). I can take a whack and do something similar for libxo. I was actually very surprised at how hard/bureaucratic it is to get a new package into Debian. FreeBSD ports and Mac Homebrew are actually way easier to work with in terms of adding a new package. However, Debian and Ubuntu have a lot of users, so it is worth the effort to push this kind of stuff through. -- Craig