Creation of a proper Mono PPA

[Alexander Trauzzi]

I wanted to separately mention the whole " fixing " of the Xamarin Debian
CI.

Is that something anyone here could do? I'm not sure what that process
would entail or how far it would necessarily get us. But maybe that's what
they want?
On 15 Jun 2014 22:38, "Christopher James Halse Rogers" <chris at cooperteam.net>
wrote:

> On Mon, Jun 16, 2014 at 12:41 PM, Alexander Trauzzi <atrauzzi at gmail.com>
> wrote:
>
>> I doubt people are interested in badgerports given many of the issues I
>> listed out originally - but most of all because it is currently at 3.2.8
>> and http://www.mono-project.org is showing 3.4.0.  I was aware of it
>> prior, it's just not going to be what anyone wants and can't be
>> realistically offered as a solution.
>>
>
> It has thousands of current users; it's clearly something that *somebody*
> wants :).
>
> It might not be exactly what you want, but this is a resource-constraint
> issue¹. Is it perhaps enough like what you want that it's not worth
> investing additional resources? Does it have a simple flaw that could be
> fixed with a little effort to make it enough like what you want?
>
> There's always going to be a lag between an upstream release and packages
> of it, unless you *don't do* any integration work. And if you want that,
> then working out why Xamarin CI's Debian autobuilder is no longer doing
> builds is almost certainly the easiest path to what you want.
>
>  I'm not really sure what you mean about the builder issues, probably
>> outside my realm of expertise/familiarity there.
>>
>> As for developers wanting to do development on current releases?
>>  Absolutely.  Would it have to be a random snapshot?  I don't think so,
>> just something >= what the mono web site indicates so that when someone
>> wants to jump in, they aren't discouraged with a second-class experience.
>>
>
> Presumably you mean ‘= what the mono web site says’; we obviously can't
> provide packages of releases that don't yet exist :)
>
>
>> I think people would be more comfortable deploying for a runtime where
>> someone is making an effort to make good quality, current releases for it
>> rather than something that shoehorns itself into /opt and doesn't integrate
>> nicely with the system.
>>
>
> Installing into /opt and not integrating with the system are orthogonal.
> As I've mentioned, we go to quite some lengths to make it easy to parallel
> install Mono runtimes and have them nicely integrated.
>
> IIRC the autobuilds in Mono CI are exactly that; integrated with the
> system, installed into /opt.
>
>
>> The node, mongodb, wine and several other very popular FOSS PPAs are
>> great examples that don't leave people going "Well this isn't what I
>> needed!".  What's available in those PPAs doesn't make the users second
>> class citizens of the community.
>>
>
> The common thread here is, of course, that all of those PPAs are
> maintained entirely *by* the community; likewise, such a Mono PPA would be.
> Sadly, these things rarely happen because someone goes “you know, it'd be
> cool if there was $THING” unless they subsequently go “so I'll start making
> $THING”.
>
> ¹: As with everything open-source. It's entirely possible for you to do
> this; if you had the resources to do it, it would be done already :)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20140615/3c7c4328/attachment.html>