Re: openbsd in general

[Stanislav Grozev <tacho@deeplaid.uni-svishtov.bg>]

> In message <199707011122.HAA01624@shandakor.tharsis.com> George Robbins writes:
> : Yeah, it would be "really nice", but with a finite development team there's
> : no point in duplicating the excellent job that the FreeBSD people have done,
> : with both their ports and packages efforts.
> 
> I have always accepted patches and tried to apply them in a timely
> manner to the FreeBSD ports tree to make life much easier for the
> OpenBSD community.  So far only Niklas has sent me patches.  Everybody
> else has just complained. I don't have the time needed to make the
> whole ports tree work on OpenBSD.  I do have the time to integrate and
> coordinate others that may want to work on a portion of the tree.  The
> FreeBSD folks have put the needed hooks into the bsd.ports.mk files to
> allow for multiple OSes to share them.  For some ports we'll need to
> have our own version of the patches because of differences in the
> underlying OS.  For most ports, they just work.  Sadly the ones that
> don't work require a bit of effort to make work outside of the FreeBSD
> environment.
> 
> So if you have patches or fixes to the ports, please lemme know!
> 

as I said before, I get my hands on this as soon as possible.
I appeal to everybody to send me, or to the maillist, a listing of
patches for FreeBSD that work with no problems on OpenBSD, for me to
concentrate only on the problematic ones...

that leaves space, besides the ports approach to have something like
a contrib tree, put in one place, as Jason has suggested. When we have
all of the ports working it will be easy to build this tree for the folks
who don't want/can compile and or collect all the stuff...


Yours truly,
         Stanislav Grozev
         (aka Tacho)
     
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 There are two ways of success:
 1. Don't reveal all your
    secrets.
 2. 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Public PGP key available on request - finger tacho@comm.uni-svishtov.bg