===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/porttest.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -c -r1.19 -r1.20
*** www/Attic/porttest.html 2005/02/09 20:37:25 1.19
--- www/Attic/porttest.html 2005/12/20 08:33:09 1.20
***************
*** 38,44 ****
! The ports tree is an huge piece of work that
permits OpenBSD users to use third-party programs without wasting time
patching, configuring and installing each one individually. This work
is done by a group of volunteers who spend their time porting and testing
--- 38,45 ----
! The ports tree is a huge piece
! of work that
permits OpenBSD users to use third-party programs without wasting time
patching, configuring and installing each one individually. This work
is done by a group of volunteers who spend their time porting and testing
***************
*** 58,64 ****
The ports tree is developed against
OpenBSD-current; there is no guarantee that
! new ports will work correctly on the other branches. This also means
you should upgrade your system and ports tree to -current
(instructions on how to do this can be found at the
anoncvs and
--- 59,66 ----
The ports tree is developed against
OpenBSD-current; there is no guarantee that
! new ports or updates will work correctly on the other branches.
! This means
you should upgrade your system and ports tree to -current
(instructions on how to do this can be found at the
anoncvs and
***************
*** 71,77 ****
There are two types of submissions on the mailing-lists; new ports
and updates. New ports are generally posted as tarball attachments
! or urls. A good idea is to extract them into the
/usr/ports/mystuff/ directory and test from there.
Updates are generally a diff against the -current ports tree, so it is best
to copy the port to mystuff/ and apply the diff to prevent tree
--- 73,79 ----
There are two types of submissions on the mailing-lists; new ports
and updates. New ports are generally posted as tarball attachments
! or URLs. A good idea is to extract them into the
/usr/ports/mystuff/ directory and test from there.
Updates are generally a diff against the -current ports tree, so it is best
to copy the port to mystuff/ and apply the diff to prevent tree
***************
*** 132,137 ****
--- 134,143 ----
Try to set the SEPARATE_BUILD variable to 'concurrent'
and test if the build still works.
Make sure dependencies on GNU make are really necessary.
+ Check whether the port is using libtool. If it is, try
+ setting USE_LIBTOOL=Yes. This way, the ports
+ infrastructure will use the libtool version in the tree, instead
+ of libtool versions that come bundled with the software's source.
regress
***************
*** 147,154 ****
--- 153,164 ----
without affecting the base system.
The port should never install files outside of the
fake directory (such as into /usr/local).
+ This kind of mistake can be easily caught by using
+ USE_SYSTRACE=Yes.
GNU libtool occasionally has trouble relinking libraries
during the fake process on some architectures.
+ Check whether all files get installed with correct ownerships
+ and permissions.
package
***************
*** 157,162 ****
--- 167,180 ----
pkg/PFRAG* are wrong.
+ lib-depends-check
+
+ - This will check whether all libraries on which the port depends
+ can be reached through either LIB_DEPENDS or WANTLIB.
+ The result should be empty. The above variables should be inspected
+ when you see lines starting "Extra" or "Missing".
+
+
install
- Packages should install all of the files from their packaging
***************
*** 211,223 ****
This will redirect the output into a log file located in the current
directory.
! Check the port Makefile for typos, incorrect links, useless or
! missing variables, correct licensing and categories.
! For those who are more skilled other targets can be tested like
! lib-depends-check, examining patches, as well as providing
! diffs to correct bugs, add flavors, or other enhancements.
These diffs should be done with the -uNr --exclude=CVS options.
cvs diff -uN can also be used to generate patches against
the CVS repository.
--- 229,245 ----
This will redirect the output into a log file located in the current
directory.
+ Finally, once the port is found to be okay, other ports depending on
+ it should also be tested, to check whether they are still working
+ correctly. The show-required-by make target will help to find
+ other ports which depend on the current one.
+
! Check the port's Makefile for correct dependencies, typos, incorrect
! links, useless or missing variables, correct licensing and categories.
! Those who are more skilled can help by examining patches, as well as
! providing diffs to correct bugs, add flavors, or other enhancements.
These diffs should be done with the -uNr --exclude=CVS options.
cvs diff -uN can also be used to generate patches against
the CVS repository.
***************
*** 225,231 ****
www@openbsd.org
! $OpenBSD: porttest.html,v 1.19 2005/02/09 20:37:25 nick Exp $