Tim, I have a vague recollection of you saying something about removing the email addresses on the scrolling list of authors. Was I halucinating? I can't seem to find the email where you said it. Now it the time to do this. Jonathan
On Sun, 2005-09-04 at 22:18 -0600, Tim Wegner wrote:
No, let's do it. Maybe even move the credits to the Docs.
I'll look at it tomorrow.
Something else we should consider is setting up an email address of bugs@fractint.org so that Robin can take down the bugslist web site. The wishlist web site could be handled in a similar fashion, although it doesn't attract the amount of traffic the buglist site does. Jonathan
Jonathan wrote:
Something else we should consider is setting up an email address of bugs@fractint.org so that Robin can take down the bugslist web site.
Already done. Any mail to bugs@fractint.org goes to me. Also fractint_sucks@fractint.org, and viagra@fractint.org :-) (I get all fractint.org domain mail not explicitly set up to go to someone else.) Seriously, this is easily done. Tim
Jonathan, I just rsynch'ed the web site (including the non-public files) to my home Mandrake box. Then I pushed the files to my public server's Fractint mirror. You've been a busy bee, I pulled down all of CVS, and it was quite a few megabytes :-) Are you now actively using CVS - should I update any changes that way? Or use our old reliable diff and patch method? In any case I need to see if permissions are correct for me to access the CVS files. Occurs to me I need to update the main fractint.org change history to reflect new developer versions. Tim
Tim,
I just rsynch'ed the web site (including the non-public files) to my home Mandrake box. Then I pushed the files to my public server's Fractint mirror.
You've been a busy bee, I pulled down all of CVS, and it was quite a few megabytes :-) Are you now actively using CVS - should I update any changes that way? Or use our old reliable diff and patch method?
Yes, I'm actively using CVS. At least, when I'm active. Yes, please use CVS for your changes. I've been generating diffs from CVS for my patches, but that may be pointless now. Does anybody apply the patches and recompile anymore? The patches are only useful for the DOS code, since Xfractint always has the source with it.
In any case I need to see if permissions are correct for me to access the CVS files.
Set your CVSROOT to: :ext:tim@mandy.fractalus.com:/home/fractint/fractcvs and the authentication method to ssh. Should work. Jonathan
I've installed WinCVS but so far can't get started at all. I also have cygwin CVS. Not to mention I could run CVS from Linux. But for the time being I am running CVS on mandy itself. I'll worry about using a remote CVS later. Otherwise you'll wait to get help from me while I'm learning about remote access to CVS. There appear to be some permission problems in the extra directory: Results of cvs checkout (second execution - presumably everything before the extra directory is OK.): cvs checkout: Updating fractint cvs checkout: Updating fractint/common cvs checkout: Updating fractint/common/cvs cvs checkout: Updating fractint/dos cvs checkout: Updating fractint/dos/cvs cvs checkout: Updating fractint/extra cvs checkout: Updating fractint/extra/cvs cvs checkout: failed to create lock directory for `/home/fractint/fractcvs/fractint/extra/cvs' (/home/fractint/fractcvs/fractint/extra/cvs/#cvs.lock): Permission denied cvs checkout: failed to obtain dir lock in repository `/home/fractint/fractcvs/fractint/extra/cvs' cvs [checkout aborted]: read lock failed - giving up Also, I was wondering about having binaries in CVS. I thought that was one of CVS's weaknesses, compared, for example, subversion. But I can see that if you want to store everything needed for a distribution zip file in CVS you'd want to do that. Tim
Tim,
There appear to be some permission problems in the extra directory:
Results of cvs checkout (second execution - presumably everything before the extra directory is OK.):
cvs checkout: Updating fractint cvs checkout: Updating fractint/common cvs checkout: Updating fractint/common/cvs cvs checkout: Updating fractint/dos cvs checkout: Updating fractint/dos/cvs cvs checkout: Updating fractint/extra cvs checkout: Updating fractint/extra/cvs cvs checkout: failed to create lock directory for `/home/fractint/fractcvs/fractint/extra/cvs' (/home/fractint/fractcvs/fractint/extra/cvs/#cvs.lock): Permission denied cvs checkout: failed to obtain dir lock in repository `/home/fractint/fractcvs/fractint/extra/cvs' cvs [checkout aborted]: read lock failed - giving up
You need to delete the lock file, since we know that nobody else is using that directory. It probably got left there when I was making changes from Illinois (done there, so at home for a while).
Also, I was wondering about having binaries in CVS. I thought that was one of CVS's weaknesses, compared, for example, subversion. But I can see that if you want to store everything needed for a distribution zip file in CVS you'd want to do that.
CVS can't merge changes to binary files. As I understand it, binary files are added to the repository and then copied, instead of merged, when they are used to check out or update to a local sandbox. I could be out to lunch, however. Jonathan
Jonathan wrote:
You need to delete the lock file, since we know that nobody else is using that directory. It probably got left there when I was making changes from Illinois (done there, so at home for a while).
I don't see a cvs.lock file anywhere. It looks to me like I don't have write permission on the directory: `/home/fractint/fractcvs/fractint/extra/cvs' Also, I need to know what the build procedure is in the DOS directory (or any of the bother directories). Since makefrac.bat is one level up, I can't just execute it. I see there is a dos.mak file. Is there a master batch build file somewhere? Tim
Tim Wegner wrote:
You need to delete the lock file, since we know that nobody else is using that directory. It probably got left there when I was making changes from Illinois (done there, so at home for a while).
I don't see a cvs.lock file anywhere. It looks to me like I don't have write permission on the directory:
`/home/fractint/fractcvs/fractint/extra/cvs'
I'll have a look. (later) Okay, I fixed it. Let me know if you run into any others.
Also, I need to know what the build procedure is in the DOS directory (or any of the bother directories). Since makefrac.bat is one level up, I can't just execute it.
I see there is a dos.mak file. Is there a master batch build file somewhere?
Using makefrac.bat should do it. Jonathan
Jonathon wrote:
I don't see a cvs.lock file anywhere. It looks to me like I don't have write permission on the directory:
`/home/fractint/fractcvs/fractint/extra/cvs'
I'll have a look. (later) Okay, I fixed it. Let me know if you run into any others.
I think I need execute permission also, still fails in the same place, with the message about extras/cvs. And while you are at it, there are other files in that extra directory that don't have full group rwx or at least rw in the case of regular files. This means I couldn't check those files into CVS. (Could probably check out).
Using makefrac.bat should do it.
Sure does work! I guess I didn't try it again after the permission problem. Great! There was one minor failure at the end of makefrac.bat, but fractint.exe got built OK. Probably has to do with the move command. I'll look into it. No rush on fixing the permission stuff, I'm off to do other things now, but I'm glad I'm beginning to be caught up with what you are doing. Tim
Tim,
I think I need execute permission also, still fails in the same place, with the message about extras/cvs. And while you are at it, there are other files in that extra directory that don't have full group rwx or at least rw in the case of regular files. This means I couldn't check those files into CVS. (Could probably check out).
I fixed the other files. The files should be rw-rw-r--. The only files that I've made executable are the binary files, and they don't really need it (object files don't execute by themselves and exe files are for DOS). The file permissions are set by the file system. So, when you check out to Linux, the permisions should end up as stated above. Since DOS has no permissions, check out doesn't matter but check in does. I've set the environment variable CVSUMASK=002 in my .bash_profile file on mandy, but this doesn't seem to have worked as I had intended. This is supposed to be the mask used when new files are created in the repository. The system umask affects this as well, and that may be the problem. Jonathan
Jonathan wrote:
I fixed the other files.
Except the one file I need fixed, the *directory* /home/fractint/fractcvs/fractint/extra/cvs needs group execute permision. I see a number of regular files with execute permission that I don't need (probably). Sorry for the trouble, but I think it will pay off to get the permissions exactly right. I'd fix it myself if I had permission :-) Tim
Tim,
I fixed the other files.
Except the one file I need fixed, the *directory*
/home/fractint/fractcvs/fractint/extra/cvs
needs group execute permision.
Ah, I see. The directories are now fixed.
I see a number of regular files with execute permission that I don't need (probably).
Sorry for the trouble, but I think it will pay off to get the permissions exactly right. I'd fix it myself if I had permission :-)
If you will recall, I was not certain I had the permissions correct when I first uploaded the repository. It's still a work in progress. 8-)) Let me know if you see any other permission problems. Jonathan
Jonathan wrote:
Let me know if you see any other permission problems.
I was able to pull all three directories (fractint, allegro, fractint- float) down OK, thanks. Hope we didn't hit Damien's host with our bandwidth usage - in the last day I rsynced fractint.org and then pulled down CVS several times. I will now delete my copy of the repository at Mandy - not needed. Tim
Tim, - I was able to pull all three directories (fractint, allegro, - fractint-float) down OK, thanks. Hope we didn't hit Damien's - host with our bandwidth usage... Nope. A one-time download seldom makes even a blip, unless it's gigabytes. You're fine. Sorry I wasn't around this weekend to take care of permissions issues for you; I was out of town meeting my girlfriend's family. / Damien M. Jones http://www.fractalus.com/gallery/ \\ dmj@fractalus.com (personal gallery of fractal art) /
From: Jonathan Osuch <osuchj@avalon.net> To: "Fractint developer's list" <fractdev@mailman.xmission.com> Date sent: Tue, 06 Sep 2005 19:36:53 -0500 Subject: Re: [Fractdev] Using CVS Send reply to: "Fractint developer's list" <fractdev@mailman.xmission.com> <mailto:fractdev-request@mailman.xmission.com?subject=unsubscribe> <mailto:fractdev-request@mailman.xmission.com?subject=subscribe>
Tim,
I think I need execute permission also, still fails in the same place, with the message about extras/cvs. And while you are at it, there are other files in that extra directory that don't have full group rwx or at least rw in the case of regular files. This means I couldn't check those files into CVS. (Could probably check out).
I fixed the other files.
The files should be rw-rw-r--. The only files that I've made executable are the binary files, and they don't really need it (object files don't execute by themselves and exe files are for DOS). The file permissions are set by the file system. So, when you check out to Linux, the permisions should end up as stated above. Since DOS has no permissions, check out doesn't matter but check in does.
I've set the environment variable CVSUMASK=002 in my .bash_profile file on mandy, but this doesn't seem to have worked as I had intended. This is supposed to be the mask used when new files are created in the repository. The system umask affects this as well, and that may be the problem.
Jonathan
_______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
Jonathan, Here's the scoop. I did manage to pull down the complete CVS to my PC. I used the brute force method of doing a recursive copy of fractcvs to /home/tim, and then doing a cvs checkout from /home/tim/fractcvs instead of /home/fractint/fractcvs. I did a checkout of the entire "fractint" module. Is that what I was supposed to do? I seem to have gotten the entire tree. What happened before was I pulled down everything up to "extras" alphabetically, and nothing thereafter. I still need to know what the DOS build procedure is. Can I build directly in my fractcvs/fractint sandbox, or do you have a script that mashes what is needed into one directory? (It really should build as it is in the sandbox). Tim
Tim Wegner wrote:
Here's the scoop. I did manage to pull down the complete CVS to my PC. I used the brute force method of doing a recursive copy of fractcvs to /home/tim, and then doing a cvs checkout from /home/tim/fractcvs instead of /home/fractint/fractcvs.
I did a checkout of the entire "fractint" module. Is that what I was supposed to do? I seem to have gotten the entire tree.
Yes, that's correct. You should have the complete source for Fractint/Xfractint. The float only source is retrieved in a similar fashion. Using tags will have the same result because I just tagged everything. It doesn't need to be that way, but it was easy. It is also handy to be able to look at the DOS specific code when trying to see how to fix the *nix specific code.
What happened before was I pulled down everything up to "extras" alphabetically, and nothing thereafter.
I still need to know what the DOS build procedure is. Can I build directly in my fractcvs/fractint sandbox, or do you have a script that mashes what is needed into one directory? (It really should build as it is in the sandbox).
Using makefrac.bat from the fractint sandbox will build Fractint. The directory magic occurs in the fractint.mak file. Jonathan
I did get tortoise cvs to work, and did have the expected permissions problem with the extra directory. But I'm way ahead of the game now. How do you mark patch numbers? With tags? Tim
Tim,
I did get tortoise cvs to work, and did have the expected permissions problem with the extra directory. But I'm way ahead of the game now.
That's what I use, also. And gcvs for Linux. I had a heck of a time recently trying to restore a file in my sandbox to the same status as in the repository. Finally managed, but it isn't intuitive.
How do you mark patch numbers? With tags?
Yes. I tried to remain consistent from one patch to the next, but that didn't always happen. Jonathan
participants (3)
-
Damien M. Jones -
Jonathan Osuch -
Tim Wegner