On Thu, Mar 13, 2003 at 02:40:31PM -0500, Kuba Ober wrote: > Your unix login, as in logged in to the terminal. ae_p is an alias for > export AEGIS_PROJECT="$1";
Oh that's OK then. > That's the whole thing. It's hard to do clean and nice development if you > cannot say what you do. You can always modify it before final integration. I assume there's a non-gui form. Why is this better than ChangeLog ? > Well, each change that you create with aenc or tkaenc gets a number. Usually, > there should be a change for each confirmed bug report at least. The job of > creating changes is quite separate from the job of actually developing the > changes. You can have different people doing creation of the changes, and > different ones doing development. Isn't the computer the one that's good with numbers ? > aecd = change directory; it simply changes the current working directory to > the root directory of the current change's (each change has its own > development directory), obviously if you feel like doing cd ~/lyx.1.4.1.C110 > instead of aecd, you're free ;-) > > aecp README = well, you have to be explicit which files are in the change; by > default you either have a development directory symlinked to a read-only > baseline, or you have a VPATH environment; either way you have to create > physical files that you're gonna edit in your development directory; that's > what aecp is for -- it copies the file from the baseline to the development > directory Well this is no good at all. It's far too much administration. What if I'm doing some work that requires some other changes that don't actually form part of the change ? (For example, I'm fixing a NO_NEXT case - I want to commit the fix but not commit the NO_NEXT turning on). At the very least I need a full source tree available directly that I can play around in. > aeb = build (only the files that you change will be rebuilt, other ones will > be used from the baseline -- that means that you don't have to notoriously > recompile everything) That's no different to now. If a header file changes then dependent files must be rebuilt > cd ~ = well, you have to exit the development directory before integration, > since after stuff is integrated the development directory will vanish And if I want to see what I just did ? I could probably survive with a system like this if I was working (as in: being paid) on something. But this sort of methodology does not agree with the whole devel/stable split. And I guarantee you that you find people just hacking around outside of this framework anyway. > the mailing list. In the Aegis model, you only need to say that the > development is done; it then awaits review and anyone can have a look at it > from the main (public) server, only when the change gets integrated it > actually affects the baseline (which is supposed to be always working, not Assuming this works properly, that would be very nice yes. john
