On 5/26/23, Blake McBride wrote:
> When I got myself in a mess with GIT, I requested help from the local "GIT
> expert." However, more often than not, they couldn't figure it out either.
Never did that in my life. I always rely on documentation, books and
myself. I'm self taught :) From my exper
Hi Peter,
thanks, generally a good idea. I will look into that. Problem is that
even the "standard places" are not standard these days. Both *apl*
and *python* could live in either /usr/include or else in
/usr/local/include
and the ./configure of GNU APL can not easily figure how python was
in
Hi Emmanuel,
the VPATH stuff is not needed for normal mortals, it is just for me to build
multiple configurations in one go. Normally you do this (all in the
top-level
directory):
1. fetch latest snapshot with subversion (*svn up*)
2. run *./configure* as discussed before
3. run *make* (should
Here is the thing for me. In the beginning, I read a little bit about
subversion. Its model, at least from a user's perspective, was simple and
straightforward. I was able to make use of it immediately. As my needs
expanded, I found simple solutions with subversion. I never got caught up
in a
On 5/26/23, Dr. Jürgen Sauermann wrote:
> I would like to share another anecdote with you.
Thanks for sharing. Now we have some experience in common and not only
in technology ;) Sorry that it happened to you. I believe that such
society is broken, but that's another matter.
Git has a distribute
I would like to share another anecdote with you.
Some years ago I worked for a company that forced me to use
git. I used to work from my home office and commit my changes
to the company's git repository. Needless to say that I use SVN
in my home office and I admit that I am not a git expert, not
