> I forgot to mention something in the previous mail. I think we should > format all the tables with a 'linux-2.6.24' $LINUX_FOLDER_NAME in the > script. That means we all should work with the same Kernel > (http://www.kernel.org/pub/linux/kernel/
One cause of this problem could be some confusion in the transition between package and kernel freedom verification. With the packages, sub-versions of sub-versions were the norm, so I can say for myself it does feel a bit unnatural to now deal with the generic 2.6.24 kernel. After all, some of us are used to downloading any kind of source via a package downloading tool with its notions of sub-versioning as opposed to the more direct wget, etc. I agree with you about standardizing. Lack of a standard complicates not only scripting but also manual efforts due to potentially inconsistent hyperlinking among pages for directories worked on by different people. Our communication becomes more complicated, too. Perhaps worst of all, some web surfers--especially novices--might get confused and question the soundness of the verification effort. A *future* ambition would be for us to communicate sub-version developments quickly and clearly. E.g., suppose a non-free file is introduced into version 2.6.24.3. Here, a "sub-versioned URL" would not involve the same potential inconsistencies as such a URL for a directory. For now, as Chris re-iterated, we should all be sticking to the generic 2.6.24 source. Regarding this, does anyone know if a "redirecting URL" would work well here? _______________________________________________ gNewSense-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/gnewsense-users
