On 02/02/2017 11:51 AM, Martin Baker wrote:
> When I'm working on a given subject area, say AlgTop, I like to have a
> small flat directory with all the working files in one place so I can
> just type things like:
> )co gpresent
> )r gpresent
> )r someLocalTest
> )co gpresentOldVersion
> That is, files that I find useful but may not be part of FriCAS.

Oh. I have not really followed deeply, but I had the impression that
gpresent.spad should become part of FriCAS. No?

I had/have a similar situation. For that I created a subdirectory and
linked (link -s) every interesting .spad file from src/algebra into that
subdir of the fricas tree (actually it could live outside if you just
use symlinks). The important thing is that the original files live at
the right place in the fricas tree. So that I can commit them into a
feature branch and rebase when it becomes necessary.

Inside my extra directory I have a file "compileall.input" that has
commands like

)compile /full/path/to/fricas/src/algebra/vector.spad
)compile /full/path/to/fricas/src/algebra/gpresent.spad

(I've explicitly mentioned vector.spad as an example. Replace
vector.spad by files that changed on trunk. You don't always need a full
recompilation of fricas.

Then you could have a file "loadall.input" that has the respective
)library commands to load the new/modified types, so that you don't
always need to start )read compileall.input.

Even files that you don't intend to add to FriCAS can live in the fricas
tree (and git repository). As long as you keep them in separate commits,
it's easy (via rebase) to separate them from what you eventually want to
make public.

You can even publish everything on your github account. As long as
nobody fetches from you, there is no problem. And if you declare that
you will freely rebase, then people will take appropriate action to get
the right commits from your repository. I would know what to do in this
case and I'm sure also Qian has no problem with a rebased branch or yours.

> I have thought that I should do this with branches but I do quite like
> the idea of having all the directories visible at the same time (so I
> can use conventional utilities like Dolphin to copy between them).

You don't need dolphin, if you use symlinks.

Try

echo "foo" > foo.txt
link -s foo.txt bar.txt
emacs bar.txt            # change the content as you like

Now look into foo.txt.

Ralf

-- 
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to fricas-devel+unsubscr...@googlegroups.com.
To post to this group, send email to fricas-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to