I had a quick look at your package. The only problem I found was that you have a '/sw' in your patch file. You should replace that with PREFIX and have it tested again.
What normally needs to be done for testing a package (written by Ben Hines <[EMAIL PROTECTED]>):
- fink validate on the .deb file and the .info file
- dpkg -c on the deb file just to make sure... make sure to do this for each splitoff.
- Check for hardcoded /sws in the info and patch (should be %p)
- Check for them touching anything outside of %d or %b during build and install. Not legal except in very special cases.
- Make sure license and Homepage is in the package and is right
- Make sure Maintainer is in the package and is the person who submitted the package. If not make sure they have the maintainer's permission.
- Check dependencies, run something like this: 'dpkg -L wml | xargs otool -L' will list all libraries linked to by everything in that package. make sure it depends on each (didnt someone make a perl script to do that?.. i think so), and make sure none are BuildDependsOnly.
- Try to check builddepends as much as possible (can be hard to get them all sometimes)
- Make sure description is readable and appropriate
- Sometimes I will let them know if they are doing crazy build hacks they don't need to be doing
- Let them know if they are missing fink fields, like if they have a .conf file but forgot ConfFiles: field, or are not using fields like ConfigureParams:
- Make sure they have splitoffs if they include shared libraries, and comply with the full -shlibs policy if necessary.
- Make sure library versions in the Shlibs: field are correct.
- python modules: must comply with fink python policy
- perl modules: must comply with fink perl module policy
You can do all that yourself. Once you think your package is ready for stable, announce it here again.
Hope that helps, Chris.
On Dienstag, Juni 3, 2003, at 04:50 Uhr, Steven Tamm wrote:
Hi *,
I'm the package maintainer for vnc-3.3.7, and a couple people were asking me how to get it migrated from unstable to stable. The list archives appear to be down so I couldn't find out for myself. The documentation talks nebulously about how the packages need to be "tested" first.
How can I get a package moved into stable?
Thanks, -Steven
------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
