Hi,
Just in case some has an interest to look into those, here are two tasks
we should look into at some point in time:
Kernel headers: according to [1], 2.6.18 will have a 'make
header_install' target, creating linux headers for glibc.
cdrkit vs cdrtools: you probably read it, the debian guys have forked
cdrtools (second fork of cdrtools after dvdrecord IIRC), and are
interested for other distributions to contribute. I don't necessarily
think that we have to become involved, but since there have been many
patches floating around made by various distros there's a chance this
projects unifies some of them. Therefore, it should be interesting to
follow this, build test ports etc.
Please speak up if you're interested in one of those tasks, otherwise
I'll queue them up.
Thanks, Johannes
References:
1. http://article.gmane.org/gmane.comp.lib.uclibc.general/12684
2. http://lists.debian.org/debian-devel-announce/2006/09/msg00002.html
--
Johannes Winkelmann mailto:jw@smts.ch
Zurich, Switzerland http://jw.smts.ch
Hey,
After some discussion with those involved in server maintenance, I'd
like to suggest Simone to be the initial leader/coordinator for the
infrastructure team; he has done a lot of work, both on the web
components (wiki/bugtracking/svnweb) and general setup.
Just to elaborate on that job: it's not meant to give him great power,
but to make sure that there's a central person to coordinate changes and
take decisions if someone else on the team is uncertain how to do it.
It's more of a "coaching" job really.
That said, we need coaches for the 'ports' team as well as for the
'core' team. CRUX maintainers, please submit your nominations :-).
Thanks for your cooperation,
Johannes
P.S. http://crux.nu/Main/TeamReorganization contains some more info
--
Johannes Winkelmann mailto:jw@smts.ch
Zurich, Switzerland http://jw.smts.ch
Hi all,
based on Johannes' ideas and performance specification [1] I've
written a simple utility, called portverify, to check CRUX ports
for typical errors.
It's a shell script which calls gawk with a bunch of small scripts,
each of them containing one or more tests.
Following test are implemented yet:
- port
- missing files Pkgfile/.footprint/.md5sum
- Pkgfile
- existence of name/version/release/source variables
- match of portname to name variable
- wrong release number
- cd/rm command outside the work directory
- .footprint
- world writable files/directories
- junk files like perllocal.pod
- invalid directories like /usr/info
- invalid users
- files not owned by root
- SUID/SGID files
To use the utility call it with one ore more ports like:
portverify /usr/ports/{core,opt}/*
All test are categorized into 4 levels, from FATAL to INFO, which
can be used to adjust the output of portverify, see the help message
for more information.
For now portverify is available from a darcs repository [2] or as
an CRUX package [3].
To do:
- missing stuff from [1]
- more test ?
- improve shell script
- man-page
- other ideas ?
Contributions and any kind of feedback are highly appreciated.
kind regards
Jürgen
[1] http://crux.nu/Main/WantedTools
[2] darcs get http://jue.ods.org/repos/portverify
[3] http://jue.ods.org/files/portverify%230.1.2.pkg.tar.gz
--
Juergen Daubert | mailto:jue@jue.li
Korb, Germany | http://jue.li/crux
