sea4th
04-25-2005, 10:07 PM
I prefer to use the cvs method to build a new release but I can only find v5_0_0_19 as a tag in cvs. Searching for "v5_0_0*" , or "cvs version" or "cvs tag" did not provide the answer. I read about cvs and piped the version info to more to see what tags were available but could not find v5_0_0_20 or 5.0.0.20 related tags.
As part of learning what SEQ is doing I will often edit the source patches or diffs manually and then recompile. But when things get out of sync it is handy to use the cvs to "reset" to a known starting point. And when SEQ breaks cvs provides the means to limp along and hopefully contribute something back to the project.
So I used the tarball and while it compiles on the speedy 233 Pentium MMX running FC2, I thought I would look some more and ended up creating this message. BTW, FC2 seems much slower than RH7.3 on a 233 and I may have to retrograde to RH7.3 and update the packages to work with SEQ.
As part of learning what SEQ is doing I will often edit the source patches or diffs manually and then recompile. But when things get out of sync it is handy to use the cvs to "reset" to a known starting point. And when SEQ breaks cvs provides the means to limp along and hopefully contribute something back to the project.
So I used the tarball and while it compiles on the speedy 233 Pentium MMX running FC2, I thought I would look some more and ended up creating this message. BTW, FC2 seems much slower than RH7.3 on a 233 and I may have to retrograde to RH7.3 and update the packages to work with SEQ.