 |
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. Hello, google. I would like to introduce you to our chat logs. Chat logs, google. Google, chat logs.
We will discuss things here such as Mono, GNOME and Debian. We may even use it to talk about work on the DLR project stuff. Tags: colliertech, debian, dlr, freenode, gnome, irc, ironpython, ironruby, linux, mono, python, washington state ubuntu loco
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. I sent an email to the Fedora Legal list asking whether they will accept software released under the MS-PL license. My friend and former colleague, Brett Lentz mentioned that he was concerned that the Fedora folks might not accept software released under the MS-PL. So I asked. I also bcc’d a certain troll on said mail so as to get lots of flame mail. I’m practicing to become a master twitterbaiter.
14:43 < cj> wakko666: so… we are building ironruby/ironpython debian packages over on OFTC/#debian-cli
14:43 < wakko666> k
14:43 < cj> meebey just packaged up mono 2.4.2.3 in .deb
14:44 < cj> with some backported patches required to get the DLR language engines running correctly
14:44 < wakko666> k
14:44 < cj> we’re using xbuild to perform the build, thanks to ankit’s recent patches.
14:44 < cj> alarm went off. need to address food.
14:44 < wakko666> i know that mono is already in Fedora.
14:45 < cj> great. any idea what version?
14:45 < wakko666> http://koji.fedoraproject.org/koji/packageinfo?packageID=30
14:45 < cj> we’ll need 2.4.2.3 + some patches. This is pretty bleeding edge, but I expect the fedora packagers are as ‘on it’ as the debian folks
14:46 < wakko666> fedora tends to be a bit further ahead of the curve than the debian folks
14:46 < cj> we can supply them the patches required. they are also being merged into the 2.4 branch, so should be in the next official release
14:46 < wakko666> k.. shouldn’t be a problem.
14:47 < cj> here is the tarball we’re using to build the .deb
14:47 < cj> http://github.com/mletterle/ironruby/tarball/20090805+git.e6b28d27
14:49 < cj> most of the stuff you’ll need as far as build commands go are in debian/rules:
http://git.debian.org/?p=pkg-cli-libs/packages/dlr-languages.git;a=tree;f=debian;h=8e4c0abc01ba2db27fe66d508317cef3b574fd3a;hb=f3c10b84cf5f12cb670d14232263ac81662ff714
14:49 < cj> I’ve got to finish making lunch for kids ;)
14:49 < cj> back shortly.
14:55 < wakko666> cj: my main concern about packaging ironruby is licensing. Fedora will accept packages under the MS-Shared-Source license [ed: this is not at all true.], but the MS-PL isn’t on their list of acceptable license. [ed: it is now.]
14:58 < cj> wakko666: alrighty. jschementi is the guy to talk with about licensing issues. He’ll be back some time soon, I’m sure
14:58 < wakko666> of course, i can always write the spec file and you guys can host your own rpms, but it would be nice to actually get it into Fedora proper.
14:59 < cj> also, MS-PL is dfsg compliant and OSL-approved. Is it a decision to deny MS-PL or that it just hasn’t been reviewed yet?
14:59 < wakko666> not sure. we’d need to ask on the fedora-legal-list mailing list
14:59 < wakko666> http://fedoraproject.org/wiki/Licensing#SoftwareLicenses
15:00 < cj> alright. at another time. it’s nap time for scarlet and zelda. ;)
15:01 < wakko666> sure thing. if you ping the fedora-legal list, let me know what they have to say.
19:49 < cj> wakko666: firestorm initiated.
Tags: c#, cli, colliertech, dlr, feds, free software, freenode, friends, git, humor, irc, ironpython, ironruby, language, linux, microsoft, mono, security, social networking, software, xbuild
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. Thanks to Marek being a superhero, we have isolated the changes necessary to fix the compiler from the 2.4.2.3 tag so that we can build IronRuby with xbuild. I’ve delivered the patch to meebey, and he has included it in his debian/patches list.
Without this patch, I was going to have to package up the pathname2 gem and add a dependency on rake and this gem. Ick. Too much work, and we planned to move to xbuild eventually anyhow, so it would have been thrown away as far as I’m concerned.
In addition to this, Ivan has committed Ankit’s character case fix patch to Michael’s git repo.
Now all I’m waiting for is the diff.gz from meebey, then I should be able to get the IronRuby packaging done and commit it to pkg-cli-libs.
But rather than sitting around and waiting for this, I should really clock some billable hours… Tags: bugs, c#, colliertech, compiler, debian, dlr, free software, irc, ironruby, mono, novell, software
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. I’m too busy to make two separate blog entries, so here is an update on my Mono work for the day.
I’ve helped get the mono-2.4.2 debs moving. The mono-api-diff tool was removed after the 2.2 branch, so I grabbed it from the attic, dusted it off and patched it for use by meebey. The solution is sub-optimal, but at least he’s able to use it get things moving again.
The other piece of news is from Ivan on the IronRuby/IronPython front. He mucked with the build script such that there are now two binary tarballs emitted. One for IronRuby, one for IronPython. I’ve fiddled with the build status report HTML template a bit and added separate links to each package. For an example, see:
http://dlrci.colliertech.org/integrity/ironruby
Keep in mind that these tarballs unpack to the current directory, so be sure to unpack in an emptry directory. I’ll ask Ivan to make this not happen in future versions, but until then: you’ve been warned. Tags: c#, colliertech, dlr, free software, irc, ironpython, ironruby, mono, software
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. Ivan has updated the build script to produce IronPython binaries as well as IronRuby. Get your fresh DLR-powered, mono-friendly, dynamic language implementations here:
http://dlrci.colliertech.org/
There are now links to source and binary tarballs as well as source zips on each of the build result status messages:
http://ironruby.colliertech.org/integrity/ironruby
I’ve been putting some effort in to getting the .deb of ironruby put together, as well. Here are the current problems :)
* xbuild in sid is not new enough to successfully build IronRuby
* rake requires a gem called pathname2, which is not otherwise packaged, and debian policy strictly disallows using ‘gem install foo’ during build
* mono 2.4.2 does not include mono-api-diff, which is keeping us from making a .deb of xbuild and friends Tags: c#, colliertech, compiler, debian, dlr, free software, freenode, irc, ironpython, ironruby, language, linux, mono, software, xbuild
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. Ivan has been doing some great work on the Mono/IronRuby continuous integration server recently. He and Ankit got xbuild support integrated, and now we have new tarballs being generated for each build. You can find them here:
http://ironruby.colliertech.org/
I’ll be using these tarballs as the ‘upstream’ source for the upcoming debian packages of IronRuby. I filed ITP for IR last year and haven’t gotten around to making it happen until now. Sorry world. Tags: c#, colliertech, debian, dlr, free software, freenode, irc, ironruby, mono, pre-release, software, xbuild
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Originally published at The Pædantic Programmer. Please leave any comments there. But then I thought better of the idea. Anyone who still takes bn seriously after the recent terrorist actions is likely not going to be swayed by facts, proof of their hypocrisy, their total lack of participation in the community and failure to engage with campaigns they claim to support.
Rather than taking the time to write something up proper, here are some questions I asked and the answers that I had to find myself, since was a curious lack of response.
12:07 < cj> 1) do you condone, condemn or have no feeling on the actions taken against Schlesinger?
http://boycottnovell.com/2009/06/12/smears-against-boycott-novell/#comment-66238
12:08 < cj> 2) What are your thoughts about patent-laden mesa code in the default desktop releases of many popular distributuions?
13:17 -BNc:#boycottnovell- [schestowitz] Truly Free Software 3D Driver for ATI/AMD Gets Better http://ping.fm/0Ly0M
12:12 < cj> 3) have you or do you plan to contribute to the Software Freedom Law Center?
http://wp.colliertech.org/cj/?p=447 Tags: abuse, c.j. insider, free software, freenode, irc, journalism, pgp, politics, spam
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
So... I've been trying to parse english language (text) for a while. I haven't quite done it yet. My new idea involves IRC bots. We have lots and lots of conversations happen in public IRC channels every day. The conversations usually involve transmission of ideas in textual format. These transmissions are quite often (but not always) understood by the receiving party. The transmissions are expected to have been intercepted by the general public, so having a bot intercept and attempt to interpret should not offend anybody :) It will anyway, of course, but we'll pretend that this 0.00001% minority doesn't mind being marginalized for the time being. So the idea is this: split the words on the standard word boundaries and do a dictionary lookup on each of them. Cache the results locally so a network hit isn't incurred for each word we look up. The info we will take from the dictionary lookup is the "part of speech" that the word falls into. In the english language, this is not often a scalar value. Computers are getting fast, so I think that this shouldn't be too much of a problem. So now we have a list of words and the parts of speech for each of these words. These words are assumed to combine in such a way that they form a coherent idea. At this point, we can create an XML document from these word elements, for instance: <sentence> <article>the</article> <noun plurality="plural">cats</noun> <verb>are</verb> <adjective>cute</adjective> </sentence> There would need to be an XSD or DTD against which to test this document in order to determine whether these parts of speech can be combined in this way to make a valid, gramatically correct, sentence. Tags: irc, language, linguistics, perl, xml
|
|
|
|
|
|
|
|
|
|
|
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
cjcollier's journal
Previous
