When considering updating or building a package the first thing I do is check to make sure we don't already have an existing srpm that can be updated: (no need to re-create the bicycle again)
Our Source packages:
http://ftp.heanet.ie/pub/pclinuxos/apt/pclinuxos/2010/
Sometimes you can rebuild a Mandriva sprm with a little tweaking for the menu entries:
(Remove epochs if found)
http://carroll.cac.psu.edu/pub/linux/distributions/mandrivalinux/devel/cooker/SRPMS/main/release/
http://carroll.cac.psu.edu/pub/linux/distributions/mandrivalinux/devel/cooker/SRPMS/non-free/release/
http://carroll.cac.psu.edu/pub/linux/distributions/mandrivalinux/devel/cooker/SRPMS/contrib/release/
Suse Packman packages can be rebuilt with some minor/major spec file editing:
(double check and fix the rpm group please)
http://packman.links2linux.org/
Rpmpbone net is another good source for srpms however most of the Fedora sprms won't uncompress on PCLinuxOS:
http://rpm.pbone.net/
I get the main ideas for how you do packaging. However, I cannot find the SRPMS for many of the packages that appear in the binary RPM format in the main repositories. I understand that the packagers may discard these when they are done, or just not upload them to the SPRM directories in the repositories.
But this poses a problem if I just want to rebuild certain RPMS from source, perhaps to build a debug version. If the packager "tweaked" a Mandriva package, how can I be assured that I will be able to "tweak" that same Mandriva source the same way the packager did? IOW, I could end up trying to debug a binary that is not really built from the same "sources" (after tweaking). This could create lots and lots of drama.
In the past, I was certain that all SRPMS were publicly available. But the locations listed in your original post do not contain, for instance, all of the qt4 source code. I do not know where your binary RPMs originally sourced from, outside of the info in the rpm -qi listings.
At any rate, I am wondering if the SRPMs could be added to the directories in the repositories. It would be nice if they were accessible from Synaptic also (I thought they were in previous releases, but perhaps my memory fails me), but that is not a necessity. The ability to retrieve the corresponding Source RPM is, though.
Thanks for your kind and patient response. (And, yes, I searched these forums high and low, and all over the Internet before I posted. I appreciate all the hard work Tex and the crew does, so I don't need a lashing. But I do admit I might be able to use some coaching on googling if I somehow missed what I am looking for. Sorry in that case ahead of time.)