Date: Mon, 3 Jan 2011 20:48:08 +0000
From: Natanael Copa <ncopa@alpinelinux.org>
To: Jeff Bilyk <jbilyk@gmail.com>
Cc: Alpine Development <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Mono package
Message-ID: <20110103204808.3cf3cf42@alpinelinux.org>
In-Reply-To: <AANLkTik_n4zC8XLsGbCOmA+AxFZ5oFMyHjdPuvbN_iHK@mail.gmail.com>
References: <AANLkTik_n4zC8XLsGbCOmA+AxFZ5oFMyHjdPuvbN_iHK@mail.gmail.com>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sat, 1 Jan 2011 22:42:28 -0500
Jeff Bilyk <jbilyk@gmail.com> wrote:

> Hey everyone,
> 
> The question came up this evening about packaging mono (the goal was
> for a web server, not for desktop .NET apps), and while the
> prerequisites as far as packages shouldn't be a problem, nenolod
> raised the legitimate question of whether it should be included in the
> main tree due to the uncertainty with patents when it comes to Mono.
> Thoughts?
> 

I would be ok with it as long as I don't need to touch it, ever.
Someone else would need to maintain it and convince me that he/she
could deliver flawless apkbuilds and updates via a public git tree that
I (or someone else with git commit access) could pull from. The
maintainer would also need to convince me he/she will stay around for a
while and keep it up to date and dealing with all apps using it.

If there are legal doubts about it we might want keep them in
the 'non-free' section.

That said, I'd rather see Java in our git tree than mono.

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---