From 55738b92634ce824f975e8a51fe2f3a4eae181bf Mon Sep 17 00:00:00 2001 From: rillig Date: Fri, 19 May 2006 21:08:42 +0000 Subject: [PATCH] The difference between submission of binary and source packages is emphasized by using two distict sections for them. --- doc/guide/files/submit.xml | 97 +++++++++++++++++--------------------- 1 file changed, 43 insertions(+), 54 deletions(-) diff --git a/doc/guide/files/submit.xml b/doc/guide/files/submit.xml index 3e9351c0d373..68b825a156b1 100644 --- a/doc/guide/files/submit.xml +++ b/doc/guide/files/submit.xml @@ -1,67 +1,56 @@ - + Submitting and Committing - -Submitting your packages - -You have to separate between binary and normal (source) -packages here: - + +Submitting binary packages - - -precompiled binary packages - - Our policy is that we accept binaries only from pkgsrc developers to - guarantee that the packages don't contain any trojan horses etc. - This is not to annoy anyone but rather to protect our users! - You're still free to put up your home-made binary packages and tell - the world where to get them. NetBSD developers doing bulk builds and - wanting to upload them please see . - - - - -packages - - First, check that your package is complete, compiles and runs well; - see and the rest of this document. Next, - generate an uuencoded gzipped &man.tar.1; archive, preferably with all files - in a single directory. - Finally, send-pr with category pkg, a - synopsis which includes the package name and version number, a short - description of your package (contents of the COMMENT variable or DESCR - file are OK) and attach the archive to your PR. - - - - If you want to submit several packages, please send a separate PR for - each one, it's easier for us to track things that way. - - - - Alternatively, you can also import new packages into pkgsrc-wip - (pkgsrc work-in-progress); see the homepage at for details. - - - + Our policy is that we accept binaries only from pkgsrc + developers to guarantee that the packages don't contain any + trojan horses etc. This is not to annoy anyone but rather to + protect our users! You're still free to put up your home-made + binary packages and tell the world where to get them. NetBSD + developers doing bulk builds and wanting to upload them please + see . + +Submitting source packages (for non-NetBSD-developers) + First, check that your package is complete, compiles and + runs well; see and the rest of this + document. Next, generate an uuencoded gzipped &man.tar.1; + archive, preferably with all files in a single directory. + Finally, send-pr with category + pkg, a synopsis which includes the package name + and version number, a short description of your package + (contents of the COMMENT variable or DESCR file are OK) and + attach the archive to your PR. + + If you want to submit several packages, please send a + separate PR for each one, it's easier for us to track things + that way. + + Alternatively, you can also import new packages into + pkgsrc-wip (pkgsrc work-in-progress); see the + homepage at + for details. + + General notes when adding, updating, or removing packages -Please note all package additions, updates, moves, and removals - in pkgsrc/doc/CHANGES. It's very important - to keep this file up to date and conforming to the existing - format, because it will be used by scripts to automatically update - pages on www.NetBSD.org - and other sites. Additionally, check the - pkgsrc/doc/TODO file and remove the entry - for the package you updated or removed, in case it was mentioned - there. + + Please note all package additions, updates, moves, and + removals in pkgsrc/doc/CHANGES. It's very + important to keep this file up to date and conforming to the + existing format, because it will be used by scripts to + automatically update pages on www.NetBSD.org and other + sites. Additionally, check the + pkgsrc/doc/TODO file and remove the entry + for the package you updated or removed, in case it was mentioned + there. When the PKGREVISION of a package is bumped, the change should appear in