We have a complete .NET application and are actively working on porting it to mono. Since we often encounter bugs in mono that the mono team fixes but do not touch mono code ourselves, we have to use anonymous cvs access. I am responsible for porting our application to mono but do not yet feel confident enough to make a cvs ebuild. It would be nice if one of the maintainers could take the time to make one. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Hi, first, you might want to make sure it runs on portable .net as well ;-) second, I doubt there are any chances for a mono-cvs ebuild, but rather for the daily snapshots they are doing for 2 weeks or so now... (see http://go-mono.com/daily) Although it shouldn't make that much difference on daily-snapshots in contrast to a cvs ebuild;) I am sure you soon hear from foser or tberman, I am mainly responsible for portable .net For various reasons we keep the number of cvs ebuilds as low as possbible, especially where they aren't really necessary ;) btw: dotgnu pnet cvs ebuilds are available at http://dev.gentoo.org/~scandium/dotgnu-pnet-cvs/
For our purposes there is no difference between daily snapshots and a cvs ebuild. Thanks for mentioning it, I wasn't aware of the daily snapshots. I will look into DotGNU portable .net project. For some reason I knew nothing about its existance. Thanks for giving me valuable information.
I personally see no reason for mono cvs ebuilds, given that releases are done quite often on a regular basis. It should be easy to adapt to current ebuilds to work with the daily snapshots Scandium mentions and writing a simple cvs ebuild isn't that complicated either if you really need it. I'm not sure there are still good examples in the live tree, otherwise we could provide you with some examples of cvs ebuilds to base it on.
Thanks for your reply. It seems that cvs ebuilds are superior to daily snapshot ebuilds because they do not require a full download of the source code every time the software is updated. In any case, I will consult developer documentation and will use the forums if I need help.
In general a live CVS ebuild is a bad idea, and in this specific case, its a horrible idea. the mono class library and internal mono runtime are undergoing rapid changes. Sometimes with cvs what it takes to compile are a bit different than another day. For example, there are times when the corlib needs to be compiled and installed before mcs, which is not the default build order. Other times certain assembly's require compilation outside of build order. And believe it or not, there are also times when its impossible to compile it with your current runtime and class library and you *have* to go download a monocharge. As far as I know the mono daily builds, and in particular the monocharge (executables and class librarys) are fairly small, and if bandwidth is your only reason for going with cvs, I recommend avoiding an ebuild and doing it by hand.
closing this
