From: "ibrahim via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Problems with git from /sys/src/cmd/git when using 9legacy-ISO (08-06-2024)
Date: Sat, 16 Nov 2024 00:59:12 -0500 [thread overview]
Message-ID: <17317367520.EBb0dddC.531171@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
When you call "mk clean" or "mk nuke" after "mk install" the build system fails with the following messages :
term% mk clean
rm -f *.[568ijqv] *.a[568ijqv] y.tab.? lex.yy.c y.debug y.output [568ijqv].??* conf get fs log query repack save send serve walk $CLEANFILES
/bin/git/add: not a git repository
mk: rm -f *.[568ijqv] ... : exit status=rc 14985: add 14987: not a git repository
term% mk nuke
rm -f *.[568ijqv] y.tab.? lex.yy.c y.debug y.output [568ijqv].??* *.acid conf get fs log query repack save send serve walk
/bin/git/add: not a git repository
mk: rm -f *.[568ijqv] ... : exit status=rc 14991: add 14993: not a git repository
Reason :
The rc script /sys/src/cmd/git/rm
#!/bin/rc -e
exec git/add -r $*
overwrites rm from /$objtype/bin
Solution :
*IF YOU USE GIT ASK THE AUTHOR FOR HIS ADVICE.*
If you don't use git as a version control and want to use the mk-System of the CD you can workarount this problem :
1) before calling "mk nuke" or "mk install"
bind -c /$objtype/bin/rm rm
2) afterwards
unmount /$objtype/bin/rm rm
Its best to do this inside a build - rc script ..
I don't know if this workaround would cause problems when you use git as version-control and have to recompile the system. I prefer CVS while using plan9 and synchronize it with a fossil-scm running on a linux machine. I prefer having ticket, wiki, documentation at one place and in a single file - but thats a question of taste.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc673fad0577438ea-M578023315c1d33f8c23d0490
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3934 bytes --]
reply other threads:[~2024-11-16 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17317367520.EBb0dddC.531171@composer.9fans.topicbox.com \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).