Future of nant, log4net, mono-sharpcvslib and mono-ndoc
by Christian Krause
Hi All!
Tom, Paul, sorry for the private mails, but you were quite involved with
these packages and so I would like to get you opinion!
The current status is, that these 4 packages don't build correctly with
mono 2.10.1. However, it looks like that nothing else requires them. ;-)
I have not investigated the build issues deeply since I got the
impression from earlier mails on this topic that these packages are more
or less obsolete anyway.
Here's my understanding from all information I gather from various
postings:
- nant seems to be still listed officially as part of the mono releases,
so it probably should stay in
- log4net and mono-ndoc should be retired
- mono-sharpcvslib could be probably retired, too (it seems to need
log4net, at least for building), but it seems to be a BR: of nant...
If we want to keep nant, I'm seeking out for some help to get it updated
to 0.90.
The straight forward way of bootstrapping it does not work since log4net
is required.
Any comments and/or suggestions are very welcome!
Best regards,
Christian
13 years
- 5
- 10
Mono 2.10.1 status report
by Christian Krause
Hi,
here is now a short update about the status of mono 2.10.1 for rawhide /
F15:
I have finished Paul's work on the mono 2.10.1 packages (in rawhide) and
it looks quite promising so far. All important packages are rebuilt and
I hope that I have solved the most annoying dependency issues.
Solved issues:
--------------
- upgrade path F15 -> rawhide works
- worst dependency issues fixed, neither f-spot nor banshee require
(indirectly) mono-devel
- banshee and f-spot seem to work
Unsolved issues, which don't block updating mono in F15:
--------------------------------------------------------
- upgrade path F14 -> F15 not tested yet, will be tested when creating
the F15 packages
- monodevelop still doesn't work correctly, but some debugging showed
that this is caused by some strange glib2 issue (Please see
https://bugzilla.redhat.com/show_bug.cgi?id=679373 for details.)
- not all dependencies are straightened out: monodevelop still needs
mono-devel (which may be OK), but e.g. banshee and f-spot still draw in
mono-extras, monodoc and mono-winforms
- future of nant, log4net and mono-ndoc unclear (I'll send out a
separate mail regarding this topic)
Next Steps:
-----------
1. "Smoke-Test" of mono 2.10.1
Please test the rawhide packages either in rawhide or in F15 (they
install without any problems from the the koji-rawhide repository):
- put the attached "fedora-rawhide-koji.repo" file into /etc/yum.repos.d/
- use these yum command line parameters: "--enablerepo rawhide-koji" for
enabling the repo when installing and/or upgrading mono packages
I suggest the following tests:
- install whatever mono application you want in F15 (_without_ the
mentioned option)
- use e.g. "yum update --enablerepo rawhide-koji 'mono*' 'f-spot'
'banshee' 'monodevelop'" to update only the mono-related packages from
rawhide/koji
- Check, whether the major applications (banshee, monodevelop, f-spot)
still work.
- Do all small tools like monodoc, monodis etc. still work?
- Does ASP.Net works?
- Can winforms applications be executed?
- Are there any strange dependencies between the various sub-packages?
- etc. etc.
- please provide all feedback on this mailing list
- later we have to decide whether any of the reported issues are
blocking the update of mono 2.10.1 in F15
2. Update mono in F15 to 2.10.1
- if there are no show-stoppers, I plan to migrate all changes done in
rawhide to F15
3. monodevelop issue
- this problem must be investigated further
- please see https://bugzilla.redhat.com/show_bug.cgi?id=679373 for details
- any help is highly appreciated
That's all for now. ;-)
Please don't hesitate to send any (positive and negative) feedback to
the mailing list.
Best regards,
Christian
13 years
- 2
- 1
- ← Newer
- 1
- Older →