This brought up another question in my mind. Is the intention to have a "GNU repository" for packages?
For binary packages, once things settle down and start working, we could host them on ftp.gnu.org. I know ideally it would just be the upstream package but how would you handle Hurd specific patches that the upstream author may or may not make? For now this is all handled in a GNU arch archive where I keep changes that are either Hurd specific, or build specific. All changes get sent upstream. Make the user patch the source themselves? No, this is handled by the GNU system creator. _ALL_ build related issues are handled by the GSC. _______________________________________________ gnu-system-discuss mailing list gnu-system-discuss@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-system-discuss
