OpenBSD Journal

New Ports of the Week #36 (September 2)

Contributed by merdely on from the putty-isnt-just-for-windows dept.

There are 12 new ports for the week of September 2 to September 8:
devel/p5-Class-Meta, devel/p5-Class-Meta-Express, devel/p5-Data-Types, devel/p5-IPC-Shareable, games/tetrinetx, mail/imapfilter, net/openvmps, net/putty, print/ijs, textproc/iksemel, www/nginx, x11/dzen2

Ports are listed in the order they were committed to the tree:

  • mail/imapfilter
    • IMAPFilter is a mail filtering utility. It connects to remote mail servers using the Internet Message Access Protocol (IMAP), sends searching queries to the server and processes mailboxes based on the results. It can be used to delete, copy, move, flag, etc. messages residing in mailboxes at the same or different mail servers. The 4rev1 and 4 versions of the IMAP protocol are supported.
  • print/ijs
    • IJS is, first and foremost, a protocol for transmission of raster page images. This snapshot provides a reference implementation of the protocol, the design of which is still in flux. When the protocol specification is published, it will be authoritative. Applications should feel free to link against the library provided in this package, adapt that code for their own needs, or roll a completely new implementation.
  • net/putty
    • PuTTY is a SSH and Telnet client implementation. This package contains the command-line clients and supporting utilities for key generation.
  • textproc/iksemel
    • iksemel is an LGPL-licensed XML parser library mainly designed for Jabber applications.
  • www/nginx
    • nginx [engine x] is a HTTP server and IMAP/POP3 proxy server.
      The basic HTTP features:
      • Handling of the static files, index files, and autoindexing
      • Accelerated reverse proxying without caching, simple load balancing and fault tolerance
      • Accelerated support without caching of the remote FastCGI servers, simple load balancing and fault tolerance
      • Modular architecture, filters including gzipping, byte ranges, chunked responses, and SSI-filter; Several subrequests in one page handling in SSI-filter via FastCGI or proxy running in parallel
      • the SSL support
      The IMAP/POP3 proxy server features:
      • User redirection to IMAP/POP3 backend using an external HTTP authentication server
      • Plain text authentication (LOGIN, USER/PASS)
      • SSL and STARTTLS support
  • games/tetrinetx
    • tetrinetx provides a server for hosting TetriNet games (a multiplayer variant of Tetris for up to six players).
  • devel/p5-IPC-Shareable
    • IPC::Shareable allows you to tie a variable to shared memory making it easy to share the contents of that variable with other Perl processes. Scalars, arrays, and hashes can be tied. The variable being tied may contain arbitrarily complex data structures - including references to arrays, hashes of hashes, etc.
  • x11/dzen2
    • Dzen is a general purpose messaging, notification and menu program for X11. It was desigend to be scriptable in any language and integrate well with window managers like dwm, wmii and xmonad though it will work with any windowmanger.
  • net/openvmps
    • OpenVMPS is a substitute implementation of Cisco Virtual Membership Policy Server (on Catalyst [65]500 family of switches). It is used on Cisco LAN switches to dynamically assign ports to VLANs according to Ethernet Address.
      Because it was developed solely on infomation obtained by observing the network traffic between switches it is probably not complete but it is a working subset of the protocol. Note that it includes a patch from openvpms CVS that fixes a logging function format string Vulnerability.
  • devel/p5-Data-Types
    • Data::Types exports a number of functions that are useful for validating and converting data types. It is intended for use in applications where data types are more important than they typically are in Perl -- e.g., database applications.
  • devel/p5-Class-Meta
    • Class::Meta provides an interface for automating the creation of Perl classes with attribute data type validation. It differs from other such modules in that it includes an introspection API that can be used as a unified interface for all Class::Meta-generated classes. In this sense, it is an implementation of the "Facade" design pattern.
  • devel/p5-Class-Meta-Express
    • Class::Meta::Express provides an interface to concisely yet expressively create classes Class::Meta. The intent is to provide a simpler, more meaningful interface for creating Class::Meta classes while preserving the power and flexibility of Class::Meta.

(Comments are closed)


Comments
  1. By Anonymous Coward (24.89.228.211) on

    I think the 'portsplus' page may be a running a commit or two off the pace =)

    http://www.openbsd.org/portsplus/index.html

    Comments
    1. By jasper@ (80.60.145.215) jasper@openbsd.org on

      > I think the 'portsplus' page may be a running a commit or two off the pace =)
      >
      > http://www.openbsd.org/portsplus/index.html

      yeah, i should really update it. but i'm too busy with other stuff. if someone can start to keep portsplus updated, contact me.

  2. By Anonymous Coward (24.91.199.196) on

    What exactly is the point of the putty port? The putty tools are just windows ports of what's already in OpenBSD by default aren't they?

    Obviously missing something...

    Comments
    1. By Anonymous Coward (74.13.33.74) on

      > What exactly is the point of the putty port? The putty tools are just windows ports of what's already in OpenBSD by default aren't they?
      >
      > Obviously missing something...

      No, putty uses some OpenSSH code, but it's not entirely a port. I honestly don't get it myself, but it is a different client, like having lsh in ports.

      Comments
      1. By Pierre Riteau (82.248.249.116) on

        > > What exactly is the point of the putty port? The putty tools are just windows ports of what's already in OpenBSD by default aren't they?
        > >
        > > Obviously missing something...
        >
        > No, putty uses some OpenSSH code, but it's not entirely a port. I honestly don't get it myself, but it is a different client, like having lsh in ports.

        Damien Miller says on ports@:

        "I'm mainly interested in this for automated interop tests for OpenSSH."

    2. By Noryungi (noryungi) on

      > What exactly is the point of the putty port? The putty tools are just windows ports of what's already in OpenBSD by default aren't they?
      >
      > Obviously missing something...

      Well, PuTTY is *the* SSH client if you are under Windows (as I am at work, alas). Besides the obvious functionalities, it offers some fairly advanced bonuses (such as character translation, keyboard mapping and obscure bug workaround) that make it one of the most pleasing SSH client ever.

      I am not exactly sure if the PuTTY port from the Linux version has all the GUI tools of the Windows version, but if it does, then you should give it a try, as it provides you with a very nice GUI manager to your different servers. As soon as OpenBSD 4.2 is out, I'll make sure to install PuTTY on some of the OpenBSD machines I have at home.

      [And, as somebody else pointed out, having PuTTY in ports provides a nice way to test its behaviour with new versions of OpenSSH]

      Comments
      1. By Brynet (Brynet) on

        While it is slighly redundant.. It has some neat features...

        You can use it as a terminal emulator.. you can use it for access serial devices.. etc.

        I've compiled this millions of times, but it's neat to have a port available..

        Unfortunately it only uses GTK1 not 2.. so it may look weird.. depending on your environment.

        Comments
        1. By sthen (85.158.44.149) on

          > You can use it as a terminal emulator.. you can use it for access serial devices.. etc.

          just like screen, then? (-:

          actually, the easy way PuTTY has to change codes generated by some of the keys (Fn, cursors etc) can sometimes be useful if you're connecting to a host with some random 10+-year-old termcap that doesn't do quite what you need...

  3. By Anonymous Coward (85.178.69.255) on

    If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".

    I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.

    I've to think about the ClamAV "update" right now...
    And others are familiar...

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

      > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
      >
      > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
      >
      > I've to think about the ClamAV "update" right now...
      > And others are familiar...

      ClamAV is up to date now. Can you point out any others you
      feel are in need of an update?

      Comments
      1. By Anonymous Coward (85.222.21.198) on

        > > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
        > >
        > > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
        > >
        > > I've to think about the ClamAV "update" right now...
        > > And others are familiar...
        >
        > ClamAV is up to date now. Can you point out any others you
        > feel are in need of an update?

        Emacs, Fluxbox.

        Comments
        1. By sthen (85.158.45.32) on

          > Emacs

          Not much response to the call for testers on ports@ in June.

          Comments
          1. By Anonymous Coward (157.24.202.211) on

            > > Emacs
            >
            > Not much response to the call for testers on ports@ in June.

            I was trying to test it but couldn't find how to update specifig packages of ports :(

            If somebody could point out where to find the info I could test the latest emacs on my T60.

            Comments
            1. By Anonymous Coward (157.24.202.211) on

              > I was trying to test it but couldn't find how to update specifig packages of ports :(
              >
              > If somebody could point out where to find the info I could test the latest emacs on my T60.

              And ofcourse I find the page just after posting above :)

              Lemme give the Emacs a go.

      2. By Anonymous Coward (64.233.230.46) on

        > > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
        > >
        > > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
        > >
        > > I've to think about the ClamAV "update" right now...
        > > And others are familiar...
        >
        > ClamAV is up to date now. Can you point out any others you
        > feel are in need of an update?

        clisp, maxima, octave and most probably others as this is not an exhaustive list just ones I can think of at the moment. However I do believe clisp is being worked on for an update which then hopefully will result in a new maxima :)

        Comments
        1. By sthen (85.158.45.32) on

          > octave

          is up to date.

      3. By Anonymous Coward (85.178.69.255) on

        > > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
        > >
        > > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
        > >
        > > I've to think about the ClamAV "update" right now...
        > > And others are familiar...
        >
        > ClamAV is up to date now. Can you point out any others you
        > feel are in need of an update?

        Well those with a 4.2 cd-Set will have to wait..?
        I wont whine but never understood that sheduling policy either.

        It also took long for the firefox update.
        It wasn't to BLAME a special port. Just wanted to list a port wich points out the "issue" of a looooooong updating circle.

        Sorry if I didn't pointed this out clearly. :/

      4. By Anonymous Coward (85.178.69.255) on

        > > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
        > >
        > > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
        > >
        > > I've to think about the ClamAV "update" right now...
        > > And others are familiar...
        >
        > ClamAV is up to date now. Can you point out any others you
        > feel are in need of an update?

        Sorry for answering 2 times but:
        Where the fuck is CLAMAV even CLOSE to anything up2date?

        It's not even up2date for 4.2! ;-[

        http://www.openbsd.org/cgi-bin/cvsweb/ports/security/clamav/?only_with_tag=OPENBSD_4_2
        http://www.openbsd.org/cgi-bin/cvsweb/ports/security/clamav/?only_with_tag=OPENBSD_4_1
        http://www.openbsd.org/cgi-bin/cvsweb/ports/security/clamav/?only_with_tag=OPENBSD_4_0

        Just "WTF"...about this comment. "Current" just doesn't count in "productiv enviroments". I just can't update the Servers 24/7 to stay "current". :-/

        Comments
        1. By sthen (85.158.44.149) on

          > Where the fuck is CLAMAV even CLOSE to anything up2date?
          > It's not even up2date for 4.2! ;-[

          the new version arrived after ports lock; the usual process is for -stable of the new release to be updated at release time.

          Comments
          1. By Anonymous Coward (85.178.127.12) on

            > > Where the fuck is CLAMAV even CLOSE to anything up2date?
            > > It's not even up2date for 4.2! ;-[
            >
            > the new version arrived after ports lock; the usual process is for -stable of the new release to be updated at release time.
            >

            So 4.0 and 4.1 gonna get released a 2nd time? *think*

        2. By Antoine Jacoutot (ajacoutot) on http://www.lphp.org

          > Sorry for answering 2 times but:
          > Where the fuck is CLAMAV even CLOSE to anything up2date?

          Oh common... any Unix admin could update clamav from source if really needed.
          As for where the fuck it is, well you'd be surprised to know how many people work on -stable ports updates... give some time.

          > It's not even up2date for 4.2! ;-[

          4.2 is not out yet.
          When it is, then clamav will be updated. What's the point in updating a software for a release that does not exist??? Does Microsoft issues updates for Windows 2015?

          > Just "WTF"...about this comment. "Current" just doesn't count in "productiv enviroments". I just can't update the Servers 24/7 to stay "current". :-/

          I run current in productive environments.
          Please use another OS.
          Your whining just make us want to just drop -stable.

      5. By Anonymous Coward (206.248.190.11) on

        > ClamAV is up to date now. Can you point out any others you
        > feel are in need of an update?

        Ocaml. 3.09 -> 3.10 is a pretty significant update, and there's some new modules that won't work with 3.09.

        Comments
        1. By Marc Espie (213.41.185.88) espie@openbsd.org on

          > > ClamAV is up to date now. Can you point out any others you
          > > feel are in need of an update?
          >
          > Ocaml. 3.09 -> 3.10 is a pretty significant update, and there's some new modules that won't work with 3.09.

          There's probably also a whole lot of shit that no longer work with a newer ocaml.

          ocaml is a pile of shit, from an engineering point of view. Each new version breaks some old stuff. Each ocaml update is a nightmare.

          The feud over the syntax between ocaml and camlp4 doesn't help. It's probably time for Xavier Leroy to finally grow up. Pity Jacques Garrigue's work had to be separate stuff for so long...

          For a mainstream language, ocaml doesn't even have a native compiler for a whole shitload of important architectures.

          Heck, we do not even have someone interested in updating the port right now, I don't think avsm has the time.

          Comments
          1. By Anonymous Coward (206.248.190.11) on

            > > > ClamAV is up to date now. Can you point out any others you
            > > > feel are in need of an update?
            > >
            > > Ocaml. 3.09 -> 3.10 is a pretty significant update, and there's some new modules that won't work with 3.09.
            >
            > There's probably also a whole lot of shit that no longer work with a newer ocaml.

            Nope, just mldonkey and one other port I can't remember off the top of my head. Both of which were easy updates.

            > ocaml is a pile of shit, from an engineering point of view. Each new version breaks some old stuff. Each ocaml update is a nightmare.

            Actually, it was quite easy to update the port and the dependant ports.

            > The feud over the syntax between ocaml and camlp4 doesn't help. It's probably time for Xavier Leroy to finally grow up. Pity Jacques Garrigue's work had to be separate stuff for so long...

            What are you talking about?

            > For a mainstream language, ocaml doesn't even have a native compiler for a whole shitload of important architectures.

            And python doesn't have a native compiler for any arch, what does that have to do with anything? I think i386, amd64, sparc, sparc64, arm32, ia64, alpha, hppa and I think some MIPS arch(es) is a pretty respectable list. I'm sure they'd welcome your contribution of a backend for vax or m68k or whatever.

            > Heck, we do not even have someone interested in updating the port right now, I don't think avsm has the time.

            Obviously not, that's kinda the problem. Would you like me to send you the update?

            Comments
            1. By Anonymous Coward (206.248.190.11) on

              > Nope, just mldonkey and one other port I can't remember off the top of my head. Both of which were easy updates.

              The other one was ocamlduce, but it was as trivial an update as you can get. Just bump the version and regen the distinfo and PLIST.

      6. By Swen (216.160.168.116) on

        > Can you point out any others you
        > feel are in need of an update?

        Wordpress - in ports is 2.2.1, 2.2.2 came out a while ago, and 3 days ago 2.2.3 came out as another security fix.

        I'd love to see a category for donations to support updating ports, and have a list of 'hot ports' that would get updated first. I don't want to make more work for the developers. But I'd be happy to donate to it.

        Comments
        1. By Anonymous Coward (63.227.38.130) on

          >
          > Wordpress - in ports is 2.2.1, 2.2.2 came out a while ago, and 3 days ago 2.2.3 came out as another security fix.
          >

          And it has been updated, thank you, port maintainers, time to make another donation.

    2. By sthen (85.158.45.32) on

      > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
      >
      > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
      >
      > I've to think about the ClamAV "update" right now...

      hmm, clamav: -current already has the latest, so you're talking about 4.0 and 4.1, right? yes, they could do with being updated, but there are more people who can work on -current than -stable, so don't think that the new ports are detracting from this.

      > And others are familiar...

      any examples? what did the MAINTAINERs say?

      Comments
      1. By Anonymous Coward (85.178.69.255) on

        > > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
        > >
        > > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.
        > >
        > > I've to think about the ClamAV "update" right now...
        >
        > hmm, clamav: -current already has the latest, so you're talking about 4.0 and 4.1, right? yes, they could do with being updated, but there are more people who can work on -current than -stable, so don't think that the new ports are detracting from this.

        Well.. do u run "current" on ya Spamfilter or the Firewall or a Fileserver? Of course there more people working on "current" then on "Stable" (this is also indicated the a OpenSSL Bug wich wasn't fixed in 4.1 yet even the Patch is in Current (well not fixed in 4.2 either I guess).

        The problem I see: Developers run current but the most "Admins" or "users" run "STABLE" (like recommented btw.!).
        Of course you code OpenBSD for yourself but without a userbase donating HW or money or so it's also not that easy to keep the project going on.
        And as I said.. "normal users" do run "STABLE". So I don't critic what's going on in "current".

        So I personaly would wish that there's at least some attention for sec. related updates... so that they get released for STABLE asap except or waiting for weeks... :-/

        I respect the OpenBSD developers VERY much and they helped me so offen (OpenBSD is just great) but it all wont help if ya Mailscanner permanently crahs 'course a Spammer abuses a known vuln to simply know ya scanner off.

        Comments
        1. By Ray Lai (216.254.116.107) ray@ on http://cyth.net/~ray/

          > Well.. do u run "current" on ya Spamfilter or the Firewall or a Fileserver? Of course there more people working on "current" then on "Stable" (this is also indicated the a OpenSSL Bug wich wasn't fixed in 4.1 yet even the Patch is in Current (well not fixed in 4.2 either I guess).
          >
          > The problem I see: Developers run current but the most "Admins" or "users" run "STABLE" (like recommented btw.!).
          > Of course you code OpenBSD for yourself but without a userbase donating HW or money or so it's also not that easy to keep the project going on.
          > And as I said.. "normal users" do run "STABLE". So I don't critic what's going on in "current".

          Normal users should not run -stable, they should run -current. Why? Because if nobody runs -current then it doesn't get tested. Then a few months pass and we have an untested -stable.

    3. By Anonymous Coward (65.34.99.75) on

      I agree with the "updated Ports" thing. For instance, I have no use for PuTTY, but there is a mission-critical app that's still broken on 4.2:
      http://archives.neohapsis.com/archives/openbsd/2006-10/1596.html
      Yes, I consider prboom mission critical. ;-) And it still bombs on E2M1 due to the same audio bug.

      For that matter, how come /usr/bin/rogue is missing on a fresh OpenBSD install of 4.2?

      $ ls /usr/games
      adventure arithmetic atc backgammon banner battlestar bcd boggle bs caesar
      canfield cfscores cribbage factor fish fortune gomoku grdc hack hangman hunt
      huntd mille monop morse number phantasia pig pom ppt primes quiz rain random
      robots rot13 sail snake snscore teachgammon tetris trek wargames worm worms
      wump

      Without DOOM and rogue, I can't get any work done! Help!

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

        > I agree with the "updated Ports" thing. For instance, I have no use for PuTTY, but there is a mission-critical app that's still broken on 4.2:
        > http://archives.neohapsis.com/archives/openbsd/2006-10/1596.html
        > Yes, I consider prboom mission critical. ;-) And it still bombs on E2M1 due to the same audio bug.

        This issue was fixed with 4.2.

        http://marc.info/?l=openbsd-ports-cvs&m=118446160312420&w=2

      2. By sthen (85.158.44.149) on

        > For that matter, how come /usr/bin/rogue is missing on a fresh OpenBSD install of 4.2?

        removed from the build in 2003: "knock these games out, i hope the licenses are fixed".

        Comments
        1. By Anonymous Coward (66.118.140.34) on

          > > For that matter, how come /usr/bin/rogue is missing on a fresh OpenBSD install of 4.2?
          >
          > removed from the build in 2003: "knock these games out, i hope the licenses are fixed".

          Why did it get removed? The license text on each file is BSD, and at the end of doc/rogue.me it says:
          "The public domain version of rogue now distributed with Berkeley UNIX
          was written by Timothy Stoehr."

          Comments
          1. By sthen (85.158.44.149) on

            > > > For that matter, how come /usr/bin/rogue is missing on a fresh OpenBSD install of 4.2?
            > >
            > > removed from the build in 2003: "knock these games out, i hope the licenses are fixed".
            >
            > Why did it get removed? The license text on each file is BSD, and at the end of doc/rogue.me it says:
            > "The public domain version of rogue now distributed with Berkeley UNIX
            > was written by Timothy Stoehr."

            Look at monster.c

    4. By Marc Espie (213.41.185.88) espie@openbsd.org on

      > If I could choose between "updated Ports" and "new Ports" I would prefere the "updated Ports" as choice. Seriously: Why including MORE AND MORE Ports if even ports (wich are propably in used by many people..?!) lack the menpower to get updated "frequently".
      >
      > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.

      You seem to think this is an `either-or' situation. Unfortunately, it's not.

      A fairly large number of ports is kept more or less up-to-date. We obviously lag behind because of the need to try out stuff, actually *use* the ports before committing updates.

      Of the other ports cited in that thread, quite a few have stumbling block issues, or are not easy updates.

      Clisp is *the* example. If it was that easy to get a working clisp port, we would have got it ages ago. Unfortunately, the GNU clisp code is not portable. It uses stuff that is dependent upon specific features that have been considered a security risk (specifically, the ability to mmap a file to an exact location... since most stuff is randomized to prevent attacks, you can't ever count on re-mapping stuff to the exact same location). So, making clisp work is fairly hard.

      Other stuff offers dubious benefits. There's been a new emacs port floating around. Nobody seems interested enough to actually test it.

      Give, give, give.

      You people apparently do not realize that, if you do not help, there is little incentive to commit updates *unless the developer wants the update*.

      Every time we ask for tests of new versions, we get zilch. Emacs is such a case.


      And yeah, it's a lot more fun to port new stuff... especially when you happen to need it.

      That said, we do know that quite a few submissions fall between the cracks. Between the stuff that's not ready to commit and needs a lot of hand-holding to get into reasonable shape (what do you mean, it has to work on something that's not i386 ? What do you mean, it has to package correctly every time), and the stuff that does not interest enough people at a given point to be committed, there are a few gems that eventually get in...

      you'll probably also notice we got a few new developers' accounts. Thus more people who can handle those submissions, so that we don't fall that far behind...

      Comments
      1. By Richard Toohey (203.167.190.49) richardtoohey@hotmail.com on

        Does Tcl fall into the same category as ocaml?

        People occasionally ask:

        http://marc.info/?l=openbsd-ports&m=115202959427179&w=2

        And submit ports:

        http://marc.info/?l=openbsd-ports&m=116116132707117&w=2

        And then nothing happens. Is this because no-one is interested in Tcl any more? Licencing? Technical problem(s)? Can someone tell me what they are?

        I want to contribute and I am learning how to do this myself (upgrade the port to 8.4.15.)

        But as it has been mentioned, it is not just the building on one arch and then strolling off into the sunset ... and if there have been changes that make it technically not worth the effort, then a bit of a pointless project.

        Thanks.

    5. By Antoine Jacoutot (ajacoutot) on http://www.lphp.org

      > I think to include new software is cool but to do it if there's not even enought menpower to update what's in the Ports it's mostly a useless move.

      All the ports I maintain are up to date. I spend a *lot* of time making sure it is (well right now, gcompris has been one release behind... for 3 days) and if not, it just means I'm working on it and the update isn't working yet.

      > And others are familiar...

      Make a list and send it to ports@ , that would give us a chance to update ports we don't personally maintain.

  4. By Anonymous Coward (64.233.230.46) on

    maybe we could get a port of
    <a href="http://wordnet.princeton.edu/">WordNet</a>

    Comments
    1. By Anonymous Coward (64.233.230.46) on

      > maybe we could get a port of > WordNet Maybe this works WordNet

      Comments
      1. By Anonymous Coward (64.233.230.46) on

        > maybe we could get a port of
        > WordNet
        >
        > Maybe this works WordNet

        Well it's getting there. Anyways I find WordNet very useful while reading etexts and it integrates with Emacs nicely :)

        Comments
        1. By sthen (85.158.45.32) on

          > Well it's getting there. Anyways I find WordNet very useful while reading etexts and it integrates with Emacs nicely :)

          I've never used it before but it looks interesting. If you're running a reasonably up-to-date snapshot, please test http://spacehopper.org/openbsd/wordnet.tgz - feedback to sthen@

          Comments
          1. By Anonymous Coward (24.37.242.64) on

            > > Well it's getting there. Anyways I find WordNet very useful while reading etexts and it integrates with Emacs nicely :)
            >
            > I've never used it before but it looks interesting. If you're running a reasonably up-to-date snapshot, please test http://spacehopper.org/openbsd/wordnet.tgz - feedback to sthen@

            Wow, talk about fast... =)

            Comments
            1. By sthen (85.158.44.148) on

              > > > Well it's getting there. Anyways I find WordNet very useful while reading etexts and it integrates with Emacs nicely :)
              > >
              > > I've never used it before but it looks interesting. If you're running a reasonably up-to-date snapshot, please test http://spacehopper.org/openbsd/wordnet.tgz - feedback to sthen@
              >
              > Wow, talk about fast... =)

              writing a port for well-behaved software like this is surprisingly quick, testing things and fixing problems that comes up usually takes the most time.

              of course, this is a fairly simple app, just a couple of dependencies and no over-complicated build infrastructure to deal with. this is not always the case...

          2. By Anonymous Coward (198.175.14.5) on

            WTF is the deal with ports requiring to be in /usr/ports/mystuff now when they aren't part of the /usr/ports tree ?

            fuck that shit.

            Comments
            1. By sthen (85.158.44.148) on

              > WTF is the deal with ports requiring to be in /usr/ports/mystuff now when they aren't part of the /usr/ports tree ?

              it's optional, but it keeps work-in-progress together (easy to rsync, which is helpful for testing multi-arch) in a dir which is .cvsignore'd, which saves trouble with Cs or broken Ms for people who later update who aren't used to merging.

              don't use it if you don't want.

  5. By Anonymous Coward (216.68.198.57) on

    Having the Ports of the week feature is great. Thank You.
    Having people do free ports is great. Thank you, however, selling this model to Corporate types really sucks. They want their own types to audit and sign off for responsibilty. GRR. Hopefully, some new business models will come around. I'm willing to wait, and help influence such a model if some want it.
    Having the ability to connect payers and porters/coders for whatever would be priceless with OpenBSD. Hopefully, this could you all.
    ~End of /etc/rant; just wishing things were more clear and simpler in IT. Life, even big $ commercial software/support is VERY unclear and problematic. Thank you to OpenBSD for paving a way, just that I want more....Life. Progress never sleeps.

    Peace all.

    Comments
    1. By Anonymous Coward (219.90.211.166) on

      > Hopefully, this could you all.

      This sentence no verb.

      Comments
      1. By Anonymous Coward (216.68.198.57) on

        > > Hopefully, this could you all.
        >
        > This sentence no verb.
        Hopefully, this could BE you all.

  6. By dukzcry (85.140.199.156) me@dukzcry.ee on

    I don't understand what cool in to have this port. It's nothing smart. It's very simply to build it from official tar.

    Comments
    1. By dukzcry (85.140.199.156) me@dukzcry.ee on

      > I don't understand what cool in to have this port. It's nothing smart. It's very simply to build it from official tar.
      I'm about NGINX web-server by Sysoev.

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.]