CookerSpot: Why packaging for GNU/Linux distributions is important ?

Why packaging for GNU/Linux distributions is important ?

they are used to click next / next / next, voilà it just works (ya the same users that usually can't read the doc' either :/ )
they do not have the time to compile (this case often happens more than one would expect : remember your first compilation ? was it easy ? should all users be obliged to compile your program, perhaps to prove they deserve to use it :-) ? )
to be matter of fact : resolving dependencies is not alway that easy (library versions, different naming scheme for libraries on different distributions meaning that name alluded to with autotools may not always be meaningful...)
some users may stop at the ./configure step, not even having the chance to encounter errors at compilation :/

to make your program more robust: among distributions variety, different architectures (ppc, x86_64, ...)
to get more testers: a new packager from one distribution is yet another experimented user that can report meaningful errors - or even provide patches - so that the upstream developers spend less time on end-user support and have more time to implement evolutions asked by end-users

first have a good description of your program, if possible with screenshots to make it as attractive as possible, identify clearly the license you chose
use a CVS or better a subversion repository to track changes you make, have a mailing-list to announce stable versions
make it simple to compile your program

provide a description for your package + icons + a menu entry
identify the list of files once compiled and where they should go (binaries, libraries, documentations, man pages, ...)

todo : find URL to submit a RFP (request for packaging)