Announcement

Collapse
No announcement yet.

Attachmate Completes Its Novell Acquisition

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • phoronix
    started a topic Attachmate Completes Its Novell Acquisition

    Attachmate Completes Its Novell Acquisition

    Phoronix: Attachmate Completes Its Novell Acquisition

    Attachmate Group has announced today that it's completed its acquisition of Novell. There were several interested parties in poaching Novell, but in the end it ended up being procured by Attachmate, as announced last November...

    http://www.phoronix.com/vr.php?view=OTM4NQ

  • manmeet005
    replied
    These chineese are trying to capture world by there cheap material and work force.

    Leave a comment:


  • yogi_berra
    replied
    Originally posted by deanjo View Post
    That still makes it a license issue, not a code issue.
    *sigh*

    Care to point out which part of this:

    oS is repackaging Wodim which is Debian's fork of cdrtools that only exists because Debian's maintainers of cdrtools had issues with Joerg Schilling and his build system, a build system which could have been replaced without the ensuing drama.
    says it was a code issue?

    Leave a comment:


  • deanjo
    replied
    Originally posted by yogi_berra View Post
    Actually, it had everything to do with the build system.

    Joerg had licensed his build scripts under the CDDL soon after the license was written which is what caused the initial bru haha within Debian. He didn't relicense any other part of cdrtools until Debian had flamed him publicly about it for several months.
    That still makes it a license issue, not a code issue.

    Leave a comment:


  • yogi_berra
    replied
    Originally posted by deanjo View Post
    Ummm no, it has NOTHING to do with the build system. It has to do with his cdrtools licensing. Feel free to search up Joerg's posts in the oS mailing lists. His troll posts are found in any one of them quite regularly.
    Actually, it had everything to do with the build system.

    Joerg had licensed his build scripts under the CDDL soon after the license was written which is what caused the initial bru haha within Debian. He didn't relicense any other part of cdrtools until Debian had flamed him publicly about it for several months.

    Leave a comment:


  • deanjo
    replied
    Feel free to read up on cdrtools relicensing to cddl. There is even a wikipedia note on it.

    http://en.wikipedia.org/wiki/Cdrtools

    Leave a comment:


  • deanjo
    replied
    Originally posted by yogi_berra View Post
    The entire community or a vocal minority?
    The community that decides to participate. Please feel free to check out openFate.


    Well, yes really, oS is repackaging Wodim which is Debian's fork of cdrtools that only exists because Debian's maintainers of cdrtools had issues with Joerg Schilling and his build system, a build system which could have been replaced without the ensuing drama.
    And so it goes.
    Ummm no, it has NOTHING to do with the build system. It has to do with his cdrtools licensing. Feel free to search up Joerg's posts in the oS mailing lists. His troll posts are found in any one of them quite regularly.

    Leave a comment:


  • yogi_berra
    replied
    Originally posted by deanjo View Post
    At one time openSUSE did offer a license decoder on it's repos. The community however decided that the core distro should be free of such blobs. This is why when you install openSUSE you do not have to click on a "Agree" button to install it after a bunch of licensing mumbo jumbo
    The entire community or a vocal minority?

    Not really, since it is not a fork. It has a distro specific patch applied to it and if the issue lies with the patch oS takes care of it. If the issue lies with the upstream package oS usually not only forwards it upstream but it also ususally is accompanied with the fix for upstream inclusion.
    Well, yes really, oS is repackaging Wodim which is Debian's fork of cdrtools that only exists because Debian's maintainers of cdrtools had issues with Joerg Schilling and his build system, a build system which could have been replaced without the ensuing drama.

    And so it goes.

    Leave a comment:


  • JanC
    replied
    Originally posted by RealNC View Post
    Oh yeah? Why doesn't it work then? All programs using SDL_mixer or SDL_sound for example, totally lack MP3 support.

    Your idea of MP3 support is limited to some media players. MP3 isn't there for just music files. There's tons of other programs and libraries where MP3 has been ripped out from them.
    Maybe SDL should make codec support plugin-based to avoid / work around the legal mess that multimedia support is (or just use GStreamer, which does that already).

    Leave a comment:


  • deanjo
    replied
    Originally posted by yogi_berra View Post
    The reason is one of the following:

    1.) Novell is too cheap to buy a patent license and give it away.
    First of all Novell is a sponsor of openSUSE as are AMD and IPExchange and many other smaller sponsors. SLE is Novells distro. The distro is community driven from the board elections to there feature requests. Also SDL_Sound uses mpg123 which has no patent license to begin with to purchase.

    2.) Lip service to RMS.
    At one time openSUSE did offer a license decoder on it's repos. The community however decided that the core distro should be free of such blobs. This is why when you install openSUSE you do not have to click on a "Agree" button to install it after a bunch of licensing mumbo jumbo

    3.) Come on how difficult is it to download and install this?
    Not difficult at all, in fact offers that very item automated with it's pullin-fluendo-mp3 package which pulls in a premade packaged rpm from fleundo in the non-oss repository.

    @ deanjo: there is a big difference between repackaging and forking because you have issues with upstream.
    Not really, since it is not a fork. It has a distro specific patch applied to it and if the issue lies with the patch oS takes care of it. If the issue lies with the upstream package oS usually not only forwards it upstream but it also ususally is accompanied with the fix for upstream inclusion.

    Leave a comment:

Working...
X