Nick Fortino <nfort...@gmail.com> posted 4a0f4ebc.5020...@gmail.com, excerpted below, on Sat, 16 May 2009 16:39:40 -0700:
> line 5 shall contain the string EAPI="arg" Given the bash expansion properties associated with double-quotes, that's not really going to work as such. What if "arg" contains $var, where $var is set in either line 3 or the environment? Now a bash parsing results in something far different than the literal string. Now that could be simply restricted out, or the more literal single-quote can be chosen instead. That saves a lot of headaches right there. As for ciaranm's argument that you're restricting changes to the version string, say allowing -rc where _rc is now required, one-time restriction of a year or two, yes. However, if the spec is crafted such that the EAPI must be checked FIRST, then after the waiting period, changes in version-string in the filename should be allowed, because the magic string checking (lines 4 and 5 in your example) can then be relied upon to be verified FIRST (well, check the extension, ebuild, without checking the rest of the filename, THEN check EAPI, which gives rules for the rest, including the rest of the filename), setting the parameters for further parsing, including of the filename version-string. That year or two one-time wait could be avoided with a single one-time extension change instead, if desired. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
