Download Chapter 2. What is NetBSD

Document related concepts
Transcript
Chapter 8. The package collection
If an error occured, it is normally pretty straightforward, here is a sample error I got while building a
package:
extract suffix not required
I did not need to define an extract suffix in the Makefile.
8.6.5. Running and Checking Build/Installs
At this point if pkglint has passed, I normally run a complete check of the fetch, build and installation.
To do this properly I must delete the work subdirectory and the distfile(s) from
/usr/pkgsrc/distfiles. This way I can ensure I will be doing a full and complete test.
8.6.6. Submitting a Package Using send-pr
First make an archive of the package tree itself (including the pkg/work subdirectory) like so:
$ tar -czf packagename.tgz package_dir
Next, upload the archive to a location that NetBSD package maintainers can access it from, if you
cannot upload the archive, contact NetBSD to see if there is some other method you might try to make
your archive available to package maintainers.
The preferred method of notifying NetBSD package maintainers is to use the send-pr utility with a
category of “pkg”, a synopsis which includes the package name and version number, a short description
of the package and the URL of the tar file.
You can use either the send-pr utility on your NetBSD system or the online form at
http://www.NetBSD.org/cgi-bin/sendpr.cgi?gndb=netbsd
(http://www.NetBSD.org/cgi-bin/sendpr.cgi?gndb=netbsd) if for some reason you cannot get send-pr to
work locally.
8.6.7. Final Notes
Again this little guide is for small packages that contain only a few files to be installed on a NetBSD
system. It makes the assumption that the package does not require any patches and can build with no
dependancies.
For more advanced issues be sure to read Packages.txt.
50