From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,8d33ebaa85598950 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.180.75.8 with SMTP id y8mr97504wiv.4.1348190011779; Thu, 20 Sep 2012 18:13:31 -0700 (PDT) Path: ed8ni3498083wib.0!nntp.google.com!feeder2.cambriumusenet.nl!feeder1.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.138.MISMATCH!xlned.com!feeder5.xlned.com!feed.xsnews.nl!border-2.ams.xsnews.nl!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!newsreader4.netcologne.de!news.netcologne.de!newsfeed.straub-nv.de!news.glorb.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: GPS issues: laundry list References: <854nn34fv2.fsf@stephe-leake.org> <1unaedlxs0o9j$.lbivg0rltyvw$.dlg@40tude.net> <85r4q62nw0.fsf@stephe-leake.org> <1b2nanavkx67n$.1rkpkv1o50bkj.dlg@40tude.net> <85d31p2g9s.fsf@stephe-leake.org> <851ui3ivac.fsf@stephe-leake.org> Date: Mon, 17 Sep 2012 17:32:38 -0400 Message-ID: <85obl4ibd5.fsf@stephe-leake.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (windows-nt) Cancel-Lock: sha1:9iFCc+4VSgBX5YawhwkQoNvXtSo= MIME-Version: 1.0 X-Complaints-To: abuse@flashnewsgroups.com Organization: FlashNewsgroups.com X-Trace: c19f0505796f6e029e66120630 X-Received-Bytes: 3697 Content-Type: text/plain Date: 2012-09-17T17:32:38-04:00 List-Id: "Dmitry A. Kazakov" writes: >> You have misunderstood what I'm proposing; I'm not editing file _names_, >> just what directory the project is checked out in. >> >> For version 07, the project is in mms_version_07/*. For version 08, the >> project is in mms_version_08/*. >> >> How else would you do it? > > I would have the stuff in a source control system. I mean a true system > which maintains consistent project views rather than merely tracking > individual files. I do; monotone. > The project (under the source control) would depend on the project > MMS, which is in some DB. You change current view from v7 to v8 by > changing the project dependency. What does that do to the directories on the disk? I'm guessing you are saying: 1) only use one directory to check out the files; say /mms 2) to change the version in the directory, use the appropriate monotone command That is certainly possible, but extremely cumbersome. First, every time you change versions, you have to recompile (unless you use a version control system that maintains compiled files, which I hate). Second, there are _many_ times when I want to compare changes between two versions, and it is much simpler to do that when both are checked out. But most importantly, I have customers using both versions (some have not upgraded yet), so I need both versions checked out and compiled. That's why I need /mms_version_07, /mms_version_08 > This is how we maintain our middleware project. It depends on hundreds of > other projects of third-party libraries, drivers etc. It would be > impossible to handle it using your way. No, it would not. If I counted all the OS libraries I use, mine probably depends on hundreds as well. In any case, that is othogonal to the issue at hand, which is how to specify ADA_PROJECT_PATH properly. >>> GPS is an IDE, it is not a language. >> >> Correct. But I can customize it by writing Python and XML, so I want >> adequate documentation to help me do that. > > Can /= must. Customizable IDE defeats the purpose of. Ok, you don't want to discuss the issue. Never mind. > This is what makes MS Developing Studio so uncomfortable. Once you > start customizing anything, you open a hell of problems how do I > manage customizations. How do I switch them, how do I store them, how > do I version them, how do I train personal on them, how do I keep them > in the incoming version of the tool... All of these problems are solved nicely by a monotone project of Emacs customizations. Well, except the 'train personel', which I accomplish by working on the same hallway ... -- -- Stephe