On Monday, July 22, 2002, at 10:29 PM, Justin Hallett wrote:
> rescan is exactly that, it's like dpkg --forget-old-unavail; dpkg > --clear-avail; dselect update when you see "Information about 1583 > packages read in 4 seconds." it's running a scan, rescan well i think > you > can figure it out > > check or validate is mostly only for developpers no real use to an > average > user > > other then the scanpackages which I agree should at list be described in > the man pages there is nothing of real interest here. > The commands available to fink users are: index, rescan, configure, bootstrap, fetch, fetch-all, fetch-missing, build, rebuild, install, reinstall, update, update-all, enable, activate, use, disable, deactivate, unuse. apropos, describe, description, desc, info, scanpackages, list, listpackages, selfupdate, selfupdate-cvs, selfupdate-finish, validate, check. checksums, cleanup. The following commands _appear_ to be synonymous: check/validate enable/activate/use/install disable/deactivate/unuse/remove/delete/purge describe/description/desc/info If it's a .deb file, the check subroutine checks for nonstandard directory usage, installing files outside of %p (/sw) Currently if /sw/src, /sw/man, /sw/info, /sw/libexec, or /sw/lib/locale are used, a warning is printed. If it's a info file, # + the filename matches %f.info # + patch file is present # + all required fields are present # + warn if obsolete fields are encountered # + warn about missing Description/Maintainer/License fields # + warn about overlong Description fields # + warn about Description starting with "A" or "An" or containing the package name # + warn if boolean fields contain bogus values # + warn if fields seem to contain the package name/version, and suggest %n/%v should be used # (excluded from this are fields like Description, Homepage etc.) # + warn if unknown fields are encountered # The most useful TODO item in this subroutine (IMHO) would be - warn if /sw is hardcoded somewhere, although the hardcoding usually occurs, in my experience, inside patched Makefiles. Perhaps the code could search the patch file for "/sw". Yes, validate is useful most to developers-- it's considered bad form to submit an .info file without validating it-- but every fink user is a potential developer. (Although a beginning fink developer runs the risk of installing files directly into /sw instead of into the the /sw/src/root-%f directory.) Perhaps the fink developers could develop a protocol for building and testing packages without requiring the use of sudo. Jeremy Jeremy ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
