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?
--
Jeff
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
On 01/01/11 19:42, Jeff Bilyk 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?>
My 2 cents on adding Mono to Alpine:
http://www.youtube.com/watch?v=StHwAffUNxo
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
Well, since it was an end-user on #-alpine-linux who raised the
question, and I don't personally have a need for mono plus adding in
the banishment of support from ncopa:) I wouldn't be the one to make
the apkbuild... I guess since I don't see Third3ye on #alpine-linux
ATM (user who requested mono) it can wait/not get built.
Jeff
On Mon, Jan 3, 2011 at 3:48 PM, Natanael Copa <ncopa@alpinelinux.org> wrote:
> 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>
--
Jeff
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
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
---