ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I need to maintain a project in CVS that was originally developed under Windows. (The compiler runs under Wine.)
Anyhow... I want to somehow designate to CVS that such-and-so project is "case insensitive," even if the underlying host system is not. In other words, I want it to interpret each filename that is checked-in or checked-out to the repository for this project in a case-insensitive manner. (Slight variations of case are a fact of life in Windows systems, where a file might be bah.EXE or bah.exe.)
"--ignore-case" is only available for the 'diff' cvs command.
So, I guess it's either hack-the-source time, or just spend the time to normalize the case in your files.
I was thinking you may be able to use the 'commitinfo' file to create a case-insensitive regex that will trap the commit and enact it on the *real* file, but the more I think about it, the more I think it would just cause an endless loop. Plus, it would only work for commits, not for checkouts.
I think the path of least resistance is just to normalize the files...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.