Comments

• Myfraudsoft

  2009-02-26 23:42:29

  Well of course, Gentoo is "eternally broken". Any non-Ballnux distro is.

• Ghazan

  2009-02-27 00:07:56

  You have been talking about big cuts at Novell coming this week, but nothing happened. Was your source, who you were so sure about, just wrong?

• Roy Schestowitz

  2009-02-27 11:54:52

  Novell could axe jobs on falling demand http://www.thewest.com.au/default.aspx?MenuId=3&ContentID=127140

• a

  2009-02-27 12:21:36

  Gentoo is broken because people who don't understand the implications of applying a specific compiler option apply it anyway. It's a known fact that GCC can break applications when aggressive optimisations are enabled. If users don't understand this, it's their fault and maybe their distros fault for not making this clear.
  
  There are many OS projects out there who won't deal with gentoo related crashes for exactly this reason.

• Dan O'Brian

  2009-02-27 12:33:54

  Your friend Balrog also refused to take suggestions on how to get it to compile.
  
  Pretty dishonest overall, not that anyone expects any less of you and your trolls.

• Ian

  2009-02-27 13:16:19

  One that’s producing Windows software like NetWare
  
  I just tried to install Netware on windows. It didn't work.

• Roy Schestowitz

  2009-02-27 13:25:40

  IPX/SPX, Windows drivers, etc.

• Balrog

  2009-02-27 13:44:39

  I was looking for suggestions in the first place (or I wouldn't be there). I didn't get any useful information overall; apparently no one knows / no one cares. Obviously, the Gentoo people blame Mono (I asked at #gentoo too) by saying it's probably buggy code (it sure seems that way).
  
  All I got from #mono was that Gentoo was doing something weird, which after checking the ebuilds, wasn't true, and the patches Gentoo applies are bugfixes that are already incorporated into trunk. Just my two cents. I want something that works, and if it doesn't, there is a need to fix it.

• Ian

  2009-02-27 13:56:21

  IPX/SPX, Windows drivers, etc.
  
  IPX is basically dead. Novell isn't a hardware company, so what drivers are they making? I don't understand what you're angling at?

• Roy Schestowitz

  2009-02-27 14:15:30

  Client side mostly.
  
  A lot of the networked environments they target are just enabling Windows clusters, at least based on my personal experience. "Windows software like NetWare" was a quickly-thrown-in phrase that I wrote in IRC and then passed over very sloppily for a blog where the key part was "Microsoft ‘plugins’ or Microsoft ‘addons’ for GNU/Linux."
  
  Novell is still dependent on Microsoft and Windows. It complements the empire of an abuser. And that was the key point.

• Acai

  2009-02-27 14:16:09

  It’s a known fact that GCC can break applications when aggressive optimisations are enabled. If users don’t understand this, it’s their fault and maybe their distros fault for not making this clear.

• Ian

  2009-02-27 14:18:41

  You're not wrong then. But you're also ignoring the fact that almost all of their customers run Windows on the workstation. Are you advocating Novell stop support Windows? If Novell considered that at any point in the near future, they might as well just lock the doors and call it now.

• Roy Schestowitz

  2009-02-27 14:23:54

  It has always made Novell an odd bedmate for S.u.S.E.

• Ian

  2009-02-27 15:03:25

  When you think about it, not really. NetWare was a dead end without a major rebuild and lacked 3rd party support. Novell's desktop strategy isn't very clear, but their server strategy is, which explains Suse.

• Dan O'Brian

  2009-02-27 15:17:54

  Balrog: First off, it's pretty dishonest of you to:
  
  1. complain when svn won't build (svn, by its very nature, is in flux) 2. not mention which revision on which branch you are even talking about 3. not mention which gcc flags you used (for mono /and/ the rest of your system, e.g. glibc, etc) 4. compiling software on gentoo is asking for problems. according to google, people have problems compiling KDE and the stability of KDE apps (and no doubt other apps) on Gentoo systems.
  
  Once again, purposely trying to fail - just like Roy's other friend who purposely tried to fail to build Moonlight so that he had an excuse to fail. And... just like him, you chose to build from svn.
  
  Dishonest? Or just retarded?
  
  I'll leave it as an exercise to the reader to decide.
  
  If you really want Mono or Moonlight, and you just *have* to compile your own instead of using packages, why not at least use released versions? Preferably source packages put together by your distro maintainers.

• Anonymous

  2009-02-27 16:42:39

  > Novell could axe jobs on falling demand
  
  You're avoiding to answer Ghazan's eligible questions. You have been touting imminent huge layoffs. So where are they? Or will you for once admit that your site is only about spreading FUD?

• Roy Schestowitz

  2009-02-27 16:49:00

  Be patient. My source was reliable.

• saulgoode

  2009-02-27 16:52:45

  If you really want Mono or Moonlight, and you just *have* to compile your own instead of using packages,...

  Isn't that *required* if anything other than Microsoft's proprietary codecs are to be used?

• Roy Schestowitz

  2009-02-27 17:03:21

  ..Which would be wiser now that Microsoft is suing Linux and looking for infringements inside it (e.g. FAT)?
  
  See this article for details.

• Balrog

  2009-02-27 17:48:49

  @Dan O'Brian: I was compiling from SVN to test out the new .NET 3 support and Silverlight 2.0 support. I'm not complaining about the build failing, but about their refusal to help and telling me to ask at #gentoo (where those people tell me it's a bug in Mono).
  
  I have used release versions, and yes, the do work (fine in Gentoo, by the way), but that's not the point here. SVN is there for testing, and if it doesn't work, troubleshooting is necessary so the maintainer can fix the problems. Seems like this wasn't the case in this situation. I used the 'moon' branch from SVN, latest rev. My gcc flags are quite standard (I'm using regular 'make' by the way).
  
  @saulgoode: Yes, you need to compile from source to use ffmpeg codecs, but not from SVN. (The ebuild for Moonlight in the gentoo portage tree doesn't have an option for proprietary codecs, by the way.) Silverlight 1.0 support does NOT require Mono, so that makes it easier. But to test the new features that are supposed to be coming soon (basically .NET 3.0 support and Silverlight 2.0 support), you need SVN mono and SVN moonlight. I understand it may be broken, but dismissing the problem and blaming the distro people isn't going to fix it.

• Gentoo User

  2009-02-27 17:57:21

  Be patient. My source was reliable.

  
  
  That wouldn't happen to be the same "source" you used here, would it?
  
  By the way,
  
  

  How does it feel to be shafted by the very same management that sold out to Steve Ballmer, who is already busy suing Linux

  
  
  Your callousness is appalling. It's easy to sit there and pontificate like this to normal people who have nothing to do with your grievances when you don't have a job to lose, a family to feed or apparently any other sort of responsibility beyond writing a blog and pretending you're important, isn't it?

• seller_liar

  2009-02-28 13:19:34

  Mono (and some other mono packages) from stable release fails a lot .Sometimes , Mono and mono packages does not detect the dependencies correctly (gtk-sharp, gtkhtml, ligdiplus and other monodevelop).
  
  Result : all autconf tests passes, but the app does not run.Or autconf does not find dependencies.(Mono packages does not use similar PATH)
  
  Monodevelop installs but does not run if some dependence have not found.The big problem is the monodevelop autconf runs 100% , but fail when try to run monodevelop