[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Ports current status
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Ports current status
- From: Marc Espie <Marc_(_dot_)_Espie_(_at_)_liafa_(_dot_)_jussieu_(_dot_)_fr>
- Date: Sun, 5 Nov 2000 19:24:19 +0100
- Mail-followup-to: ports_(_at_)_openbsd_(_dot_)_org
We are currently churning out packages for the 2.8 CD, and the ports tree
is now final for 2.8 (tagged and branched).
I think we are going to stay with the ports tree locked for a little while
- it would be great if a very large set of packages for various architectures
were to show up on ftp.openbsd.org once 2.8 is out.
- I'd like some large scale testing of these to happen, and packaging bugs
to be fixed, at least for the packages available through ftp.
- there are STILL a few broken ports in the ports tree. Specifically:
===> gom-0.29.103 is marked as broken: check out gomconfig....
===> xmcd-2.3 is marked as broken: spinlocks in a loop if stdin is null.
===> xmp-1.1.5 is marked as broken: Obvious tmp race in api/load.c, to fix.
===> bpl+-1.0 is marked as broken: Tmpnam() warning is a genuine problem.
===> hylafax-4.0.2-letter is marked as broken: Security hole (buffer overflow
yielding setuid uucp).
===> mgetty-1.1.21 is marked as broken: insecure tempfile handling: can
overwrite any file on the system.
===> tkhylafax-3.0 is marked as broken: required dependencies not available.
===> fxtv-1.02 is marked as broken: security issues with tempnam(), to fix.
===> pgpsendmail-1.4.5 is marked as broken: bombs in the fake process..
===> pine+pico-4.21 is marked as broken: remote access exploit.
===> wide-dhcp-220.127.116.11 is marked as broken: Never update anything in /etc
without asking the user first..
so, I'm considering not unlocking until at least a few of these are fixed,
as an incentive for the ports team to work.
Note that, as of OpenBSD 2.8, we have a stable ports branch.
When fixed packages are provided, some adjustements will need to be made:
- if the package source changed, the package name will appear newer.
- if the package source didn't change, the PKGNAME will be adjusted from
foo-x.y to foo-x.yp1, to denote the first patched version, etc.
That way, it should be obvious to know whether the packages on your machine
I currently have 901 packages sitting in my laptop's package directory
(e.g., 901 packages do build correctly, and most should be usable).
854 should be available for ftp.
This is for i386. Other architectures can potentially churn out very similar
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
Visit your host, monkey.org