Quote:
Originally Posted by israel2k9
the package is okey; make a test!!!
|
With all due respect for your work on these packages but your reply addresses none of the questions asked.
One of the basic rules is to only install packages from "trusted" vendors and people who know how to make packages (like the RPMForge people).
If you intended these packages as a spin-off from the official ones and you intend to continue producing or supporting them you best set up a permanent home for your packages (say Sourceforge or Savannah), and set up a bug tracker and a forum or mailing list for people to reach you.
With respect to your packages you should refer people to the aMSN Wiki that lists the steps to build the anti-aliased version of aMSN, list your dependencies and any steps that are different from the "official" build rules, provide the source packages and buildfiles and logs, sign packages with your GPG-key where possible and provide MD5 hashes for packages.
About using "--no-deps", that is a really bad move because it means you deliberately sidestep dependencies. That should *not* be used unless people are onehundred percent sure it doesn't result in crashes or other errors. If it's because of your package building skills then I suggest you learn from official packagers. Most of them have mailing lists you can ask questions on.
OTOH, if these packages are really one-offs and you do not intend to continue producing or supporting them you should aim for the support from the official aMSN developer or maintainer (which you should do anyway). Submit the packages and have him/her validate and list your packages on the official site.
If you are not willing to pursue any of these approaches, then what valid reasons do people have to trust your packages?
