OpenBSD Journal

OpenOffice packages available

Contributed by deanna on from the more-spare-cycles dept.

Due to the incredible amount of work that has gone into the OpenBSD-native OpenOffice.org port, it has been announced that i386 binary packages containing numerous improvements are now available.

Congratulations and thank you!

(Comments are closed)


Comments
  1. By Anonymous Coward (64.142.92.182) on

    Wow this is great! Six months ago, I had to use Open Office on Windows to view some Power Point files. Now I can view the same files just fine under OpenBSD. Thanks so much for your hard work guys, this rocks. As much as OpenOffice stinks, it is indeed very useful for reading Microsoft documents.

    Comments
    1. By Anonymous Coward (206.109.19.80) on

      > Wow this is great! Six months ago, I had to use Open Office on Windows to view some Power Point files. Now I can view the same files just fine under OpenBSD. Thanks so much for your hard work guys, this rocks. As much as OpenOffice stinks, it is indeed very useful for reading Microsoft documents.

      You can still run OpenOffice (Linux) under emulation, which works very well.

      Comments
      1. By Anonymous Coward (64.142.92.182) on

        > > Wow this is great! Six months ago, I had to use Open Office on Windows to view some Power Point files. Now I can view the same files just fine under OpenBSD. Thanks so much for your hard work guys, this rocks. As much as OpenOffice stinks, it is indeed very useful for reading Microsoft documents.
        >
        > You can still run OpenOffice (Linux) under emulation, which works very well.

        I tried that, it crashed on the Power Point files I was opening.

  2. By Anonymous Coward (195.29.148.251) on

    Yesterday I built OOo from ports tree (OpenBSD 4.0) on my Thinkpad X31. It works like a charm but initially "make" had a problem fetching source tarball (i think it was openoffice-2.0.3m179p0). As "make" didn't suceed fetching it, I found and fetched it manually and put it into /usr/ports/distfiles/. Afterwards, a "make install clean" was everything I needed (and a good night's sleep :-)

    Thank you guys !

    Comments
    1. By Kurt Miller (69.122.119.232) on

      > Yesterday I built OOo from ports tree (OpenBSD 4.0) on my Thinkpad X31. It works like a charm but initially "make" had a problem fetching source tarball (i think it was openoffice-2.0.3m179p0). As "make" didn't suceed fetching it, I found and fetched it manually and put it into /usr/ports/distfiles/. Afterwards, a "make install clean" was everything I needed (and a good night's sleep :-)
      >
      > Thank you guys !

      The OOo port in the 4.0 release ports tree was a work-in-progress and has some significant issues (deadlocks / Save As not working, etc). That's why it wasn't connected to the build and no package was created.

      The most recent snapshot combined with snapshot packages will give you a fully working OOo. Send a note to ports@ if you find issues with the -current OOo package.

      Comments
      1. By Anonymous Coward (195.29.157.74) on

        > > Yesterday I built OOo from ports tree (OpenBSD 4.0) on my Thinkpad X31. It works like a charm but initially "make" had a problem fetching source tarball (i think it was openoffice-2.0.3m179p0). As "make" didn't suceed fetching it, I found and fetched it manually and put it into /usr/ports/distfiles/. Afterwards, a "make install clean" was everything I needed (and a good night's sleep :-)
        > >
        > > Thank you guys !
        >
        > The OOo port in the 4.0 release ports tree was a work-in-progress and has some significant issues (deadlocks / Save As not working, etc). That's why it wasn't connected to the build and no package was created.
        >
        > The most recent snapshot combined with snapshot packages will give you a fully working OOo. Send a note to ports@ if you find issues with the -current OOo package.


        Ok, the situation is like this: the port is not stable, I don't want to track snapshot solely for OOo purposes, and linux emulation is not native.

        So, what's the best solution for using OOo on OpenBSD 4.0-stable ?

        Comments
        1. By Brad (216.138.195.228) brad at comstyle dot com on

          > > > Yesterday I built OOo from ports tree (OpenBSD 4.0) on my Thinkpad X31. It works like a charm but initially "make" had a problem fetching source tarball (i think it was openoffice-2.0.3m179p0). As "make" didn't suceed fetching it, I found and fetched it manually and put it into /usr/ports/distfiles/. Afterwards, a "make install clean" was everything I needed (and a good night's sleep :-)
          > > >
          > > > Thank you guys !
          > >
          > > The OOo port in the 4.0 release ports tree was a work-in-progress and has some significant issues (deadlocks / Save As not working, etc). That's why it wasn't connected to the build and no package was created.
          > >
          > > The most recent snapshot combined with snapshot packages will give you a fully working OOo. Send a note to ports@ if you find issues with the -current OOo package.
          >
          >
          > Ok, the situation is like this: the port is not stable, I don't want to track snapshot solely for OOo purposes, and linux emulation is not native.
          >
          > So, what's the best solution for using OOo on OpenBSD 4.0-stable ?

          The port wasn't meant to be stable at that point. It was an initial port and very rough work in progress. That is why it wasn't hooked up to the build system to provide packages.

          The only option you have if you want native OOo is to use a snapshot
          with snapshot packages.

        2. By Anonymous Coward (68.104.220.48) on

          > > The most recent snapshot combined with snapshot packages will give you a fully working OOo. Send a note to ports@ if you find issues with the -current OOo package.
          >
          >
          > Ok, the situation is like this: the port is not stable, I don't want to track snapshot solely for OOo purposes, and linux emulation is not native.
          >
          > So, what's the best solution for using OOo on OpenBSD 4.0-stable ?

          You have three options; wait for 4.1, track -current on 4.0, or go with linux emulation. Only one of those lets you stick with 4.0-stable. Native or not, that's why the emulation components are there is for situations like this.

  3. By Anonymous Coward (82.64.82.156) on

    It's really usefull to have an OpenOffice package
    when you want to run OpenBSD as a desktop operating
    system for example. Great job, developpers :)

    Comments
    1. By bsdfun (83.84.118.41) on

      We work on a complete office environment based on OpenBSD for servers and workstations/laptops. We will start soon with 50+ users and the final target will be around 1000+ users.

      > It's really usefull to have an OpenOffice package
      > when you want to run OpenBSD as a desktop operating
      > system for example. Great job, developpers :)

  4. By nikns (89.191.97.92) nikns@secure.lv on

    Thanks to everyone involved with native openoffice port. Robert, Kurt, Ian and others!

    Comments
    1. By djm@ (203.217.30.85) on

      > Thanks to everyone involved with native openoffice port.
      > Robert, Kurt, Ian and others!

      Yeah, an amazing job. Great work!

    2. By Anonymous Coward (68.104.220.48) on

      > Thanks to everyone involved with native openoffice port. Robert, Kurt, Ian and others!

      I second. Looking at the patches gives me a bleeding migraine thinking of all the work it took. Thanks for doing it.

      A bloody shame the app couldn't have been designed a bit more portable up front in the first place...

      Comments
      1. By Anonymous Coward (156.34.219.207) on

        > A bloody shame the app couldn't have been designed a bit more portable up front in the first place...

        Yes ... the fact that it took so many developers, patches, and hours of work to get a usable port on a 'ix platform (we aren't talking an radically differenet OS or something ...) doesn't exactly fill me with confidence as the to quality of the code in the first place! Personally, I'm a LaTeX person, but my hat is off to all those contributing to the port anyway for a job well done!

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]