Krisbee wrote:
> Pascal,
>
> I really think Triode would expect non-developers (that's me) to simply
> clone the "soa-aur repository" on github with a git clone command, and
> then update their local copy with a git pull as and when notified of
> changes/updates via this thread until advised of an alternative
> mechanism. If your local copy is corrupted in any way, it's small
> enough to just re-clone it.
>
> Right now, the only change I can think an end-user might want to make is
> to comment out the "jivelite-autologin" stanza in soa-install.sh before
> running soa-install.sh. You could just copy soa-install.sh to say,
> mysoa-install.sh. Edit and then run mysoa-install.sh, and then delete
> it, then git should not, I think, complain when you do a git pull. Of
> course, you could change any file(s) that result from the makepkg
> commands as they don't form part of the github repo.
>
> I found a couple of webrefs:
>
> The very basic concepts : http://rogerdudler.github.io/git-guide/
>
> A lot more detailed: http://gitref.org/ (I really wouldn't expect a
> non-devleoper to need this)
Actually looks like my fault... The build process may update one or
more of the files which git originally downloaded and so "git pull"
won't run without you doing something else first. For the moment if you
get then then type:
Code:
--------------------
git commit -a -m "!"
--------------------
This just accepts the change and allows you to then run git pull. I'll
add this to the soa-update.sh script and look at whether I can make it
simpler...
------------------------------------------------------------------------
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
