On Thu, Dec 23, 2004, Doug Summers wrote:

> I would like to see the following open-source packages added to OpenPKG
> (if possible, of course):
>
> OpenAFS (especially one that works with 2.6 Linux kernels)
> Logrotate (unless something similar already exists)
> TightVNC (add server version)
>
> After the holidays I'm going to be hitting up my company to dedicate
> some resources to this project. Hopefully I can convince them of
> OpenPKG's worth.

Just a few notes on the above software:

- OpenAFS: a great thing I would like to see myself. Unfortunately
  it certainly requires an OS-dependent part (as it's the case for
  similar filesystems like Coda, etc) and AFAIK it is currently only
  ported to Linux and Solaris but not to FreeBSD and some other
  important (for us) onces. Hence a really portable OpenPKG package will
  be hard to create out of it at the current stage. But ok, better than
  having no OpenAFS at all...

- Logrotate: a nice and popular thing and certainly worth to package,
  although OpenPKG packages for their own purposes by design use "shtool
  rotate" which is mainly a super-set of all log rotation functionality.
  But for external purposes (user logfiles) it would be nice to have, of
  course.

- TightVNC: the server part depends on the availability of the X11 server
  sources AFAIK. This in itself is not a problem, except that the X11
  servers sources are large and perhaps a little bit too hardware
  specific (and less portable than expected). At least these were the
  reasons I initially left out the server part. I would be happy if
  someone can add it without attaching the whole 50MB X.Org sources to
  the small TightVNC package... ;-)

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com

______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      [email protected]

Reply via email to