threads / bug / 6334

[BUG] OSX ends with "install: git-init.1: No such file or directory"

Subject: [BUG] OSX ends with "install: git-init.1: No such file or directory"

## tl;dr

4 messages between Jan 11, 2007 and Jan 11, 2007.

replies: 3people: 3as markdown or json

Randal L. Schwartz· Jan 11, 2007, 05:51 UTC · lore

    install -m644 git-add.1 git-am.1 git-annotate.1 git-apply.1 git-applymbox.1 git-applypatch.1 git-archimport.1 git-archive.1 git-bisect.1 git-blame.1 git-branch.1 git-cat-file.1 git-check-ref-format.1 git-checkout-index.1 git-checkout.1 git-cherry-pick.1 git-cherry.1 git-clean.1 git-clone.1 git-commit-tree.1 git-commit.1 git-convert-objects.1 git-count-objects.1 git-cvsexportcommit.1 git-cvsimport.1 git-cvsserver.1 git-daemon.1 git-describe.1 git-diff-files.1 git-diff-index.1 git-diff-stages.1 git-diff-tree.1 git-diff.1 git-fetch-pack.1 git-fetch.1 git-fmt-merge-msg.1 git-for-each-ref.1 git-format-patch.1 git-fsck-objects.1 git-gc.1 git-get-tar-commit-id.1 git-grep.1 git-hash-object.1 git-http-fetch.1 git-http-push.1 git-imap-send.1 git-index-pack.1 git-init-db.1 git-init.1 git-instaweb.1 git-local-fetch.1 git-log.1 git-lost-found.1 git-ls-files.1 git-ls-remote.1 git-ls-tree.1 git-mai
 linfo.1 git-mailsplit.1 git-merge-base.1 git-merge-file.1 git-merge-index.1 git-merge-one-
 file.1 git-merge-tree.1 git-merge.1 git-mktag.1 git-mktree.1 git-mv.1 git-name-rev.1 git-p4import.1 git-pack-objects.1 git-pack-redundant.1 git-pack-refs.1 git-parse-remote.1 git-patch-id.1 git-peek-remote.1 git-prune-packed.1 git-prune.1 git-pull.1 git-push.1 git-quiltimport.1 git-read-tree.1 git-rebase.1 git-receive-pack.1 git-reflog.1 git-relink.1 git-remote.1 git-repack.1 git-repo-config.1 git-request-pull.1 git-rerere.1 git-reset.1 git-resolve.1 git-rev-list.1 git-rev-parse.1 git-revert.1 git-rm.1 git-runstatus.1 git-send-email.1 git-send-pack.1 git-sh-setup.1 git-shell.1 git-shortlog.1 git-show-branch.1 git-show-index.1 git-show-ref.1 git-show.1 git-ssh-fetch.1 git-ssh-upload.1 git-status.1 git-stripspace.1 git-svn.1 git-svnimport.1 git-symbolic-ref.1 git-tag.1 git-tar-tree.1 git-unpack-file.1 git-unpack-objects.1 git-update-index.1 git-update-ref.1 git-update-server-info.1 git-up
 load-archive.1 git-upload-pack.1 git-var.1 git-verify-pack.1 git-verify-tag.1 git-whatchan
 ged.1 git-write-tree.1 gitk.1 /opt/git/man/man1
    install: git-init.1: No such file or directory
    make[1]: *** [install] Error 71
    rm git-init.xml
    make: *** [install-doc] Error 2

If I cd into Documentation, and try to make "git-init.1", I get this:

    % make git-init.1
    asciidoc -b docbook -d manpage -f asciidoc.conf git-init.txt
    xmlto -m callouts.xsl man git-init.xml
    Note: meta date   : No date. Using generated date       git-init-db
    Note: meta source : No productname or alternative       git-init-db
    Note: meta source : No refmiscinfo@class=source         git-init-db
    Note: meta version: No productnumber or alternative     git-init-db
    Note: meta version: No refmiscinfo@class=version        git-init-db
    Warn: meta source : No valid fallback. Leaving empty    git-init-db
    Note: meta manual : No ancestor with title              git-init-db
    Note: meta manual : No refmiscinfo@class=manual         git-init-db
    Warn: meta manual : No valid fallback. Leaving empty    git-init-db
    Note: Writing git-init-db.1
    rm git-init.xml

That's not good. Making git-init-db when it wants git-init.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

Junio C Hamano· Jan 11, 2007, 06:47 UTC · re: Randal L. Schwartz · lore

Re: [BUG] OSX ends with "install: git-init.1: No such file or directory"

merlyn@stonehenge.com (Randal L. Schwartz) writes:

Show 18 quoted lines

> If I cd into Documentation, and try to make "git-init.1", I get this:
>
>     % make git-init.1
>     asciidoc -b docbook -d manpage -f asciidoc.conf git-init.txt
>     xmlto -m callouts.xsl man git-init.xml
>     Note: meta date   : No date. Using generated date       git-init-db
>     Note: meta source : No productname or alternative       git-init-db
>     Note: meta source : No refmiscinfo@class=source         git-init-db
>     Note: meta version: No productnumber or alternative     git-init-db
>     Note: meta version: No refmiscinfo@class=version        git-init-db
>     Warn: meta source : No valid fallback. Leaving empty    git-init-db
>     Note: meta manual : No ancestor with title              git-init-db
>     Note: meta manual : No refmiscinfo@class=manual         git-init-db
>     Warn: meta manual : No valid fallback. Leaving empty    git-init-db
>     Note: Writing git-init-db.1
>     rm git-init.xml
>
> That's not good. Making git-init-db when it wants git-init.

Not good.  I am _very_ tempted to do this.

;-)

---

diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 36838c7..30d9834 100644
--- a/Documentation/git-init.txt
+++ b/Documentation/git-init.txt
@@ -1 +1,17 @@
-include::git-init-db.txt[]
+git-init(1)
+===========
+
+NAME
+----
+git-init - Creates an empty git repository
+
+SYNOPSIS
+--------
+'git-init' [--template=<template_directory>] [--shared[=<permissions>]]
+
+
+DESCRIPTION
+-----------
+
+This is a silly synonym for gitlink:git-init-db[1].  Learn to use that
+command instead.

Andreas Ericsson· Jan 11, 2007, 09:57 UTC · re: Junio C Hamano · lore

Re: [BUG] OSX ends with "install: git-init.1: No such file or directory"

Junio C Hamano wrote:

Show 23 quoted lines

> merlyn@stonehenge.com (Randal L. Schwartz) writes:
> 
>> If I cd into Documentation, and try to make "git-init.1", I get this:
>>
>>     % make git-init.1
>>     asciidoc -b docbook -d manpage -f asciidoc.conf git-init.txt
>>     xmlto -m callouts.xsl man git-init.xml
>>     Note: meta date   : No date. Using generated date       git-init-db
>>     Note: meta source : No productname or alternative       git-init-db
>>     Note: meta source : No refmiscinfo@class=source         git-init-db
>>     Note: meta version: No productnumber or alternative     git-init-db
>>     Note: meta version: No refmiscinfo@class=version        git-init-db
>>     Warn: meta source : No valid fallback. Leaving empty    git-init-db
>>     Note: meta manual : No ancestor with title              git-init-db
>>     Note: meta manual : No refmiscinfo@class=manual         git-init-db
>>     Warn: meta manual : No valid fallback. Leaving empty    git-init-db
>>     Note: Writing git-init-db.1
>>     rm git-init.xml
>>
>> That's not good. Making git-init-db when it wants git-init.
> 
> Not good.  I am _very_ tempted to do this.
>

Perhaps, but "git init-db" does a lot more than just initialise the object database (such as setting default config-variables, installing template hooks...). "git init" is actually a more sensible name now adays.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Junio C Hamano· Jan 11, 2007, 23:53 UTC · re: Andreas Ericsson · lore

Re: [BUG] OSX ends with "install: git-init.1: No such file or directory"

Andreas Ericsson <ae@op5.se> writes:

> Perhaps, but "git init-db" does a lot more than just initialise the
> object database (such as setting default config-variables, installing
> template hooks...). "git init" is actually a more sensible name now
> adays.

Thanks.  That's the "excuse" I was hoping to come from somewhere ;-).

In general, I do not like any change, and I do not see much point in renaming init-db to init. Granted, other people may be used to see "scm init", but that is not a strong enough reason for _me_ to sell the name change to old-timers.

So let's do this instead.

 (1) Documentation/git-init.txt will have the full
     documentation, and we mention init and init-db are
     synonyms;

 (2) We refer people to gitlink:git-init[1] from
     Documentation/git-init-db.txt