edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Geoff McLane <ubuntu@geoffair.info>
Cc: Adam Thompson <arthompson1990@gmail.com>,
	edbrowse-dev@edbrowse.org, Alfonso Siciliano <alfix86@gmail.com>
Subject: Re: [edbrowse-dev] documentation respecting install prefix in cmake
Date: Thu, 26 Dec 2019 21:51:00 +0100	[thread overview]
Message-ID: <20191226205100.GA26919@nautica> (raw)
In-Reply-To: <460ad829-de45-7788-f776-bcd37c65a0de@geoffair.info>

Hi Geoff,

Geoff McLane wrote on Thu, Dec 26, 2019:5B
> I started to look around at various other projects I can compile with CMake...
> find a lot of sometimes confusing, even contradictory... information...

That seem to be a recurring problem with build systems as new versions
come out...
If the MAN_INSTALL_DIR and co have been defined for enough versions I
think it is better, but it does not look like a default variable to me,
something to do with KDE install dirs perhaps?
At this point I think the ideal solution would be using GNUInstallDirs's
MANDIR and DOCDIR as I suggested earlier, but the safest would be as
little change as possible like I had done.

> why do we have 2 slightly different UnixManFile... debian vs freebsd...
> are the man app implementations /SO/ different... in a quick review, seems
> they could be one...

That is a good question, it looks like Alfonso Siciliano preferred
adding a freebsd man page to using the debian one from the git log?
I have added him in exlpicit CCs to this mail.

> And they could use like @EDB_VERSION@, @VER_DATE@, etc... even say a
> @DOC_INSTALL@, for the usersguide.html pointer... etc... etc...
> It seems the cmake default CMAKE_INSTALL_PREFIX of "/usr/local" is
> generally agreed as the /ROOT/...
> So others components are "/ROOT/bin, lib, include"
> And then the man being "/ROOT/share/man/man1"...
> But it looks like some distros prefer "/ROOT/man/man1", which
> would also be ok in my Ubuntu debian based linux, in that there is
> a link "man -> share/man" ... must look in my Raspian RPI...
> Then the docs to "/ROOT/share/doc/<project>"...

Ah, I had missed that FreeBSD wanted the man page in /usr/local/man
(without /share/) in our CMakeLists.
Looking at the FreeBSD release notes[1] that are a bit difficult to
read, the man pages should go either to /usr/share/man if the prefix is
/usr but if it is /usr/local then it should go directly to
/usr/local/man for some reason... Odd... But that means my fix is
I just checked and the MANDIR variable from GNUInstallDirs has the
correct exception for all BSDs, so I will update my patch to use that

[1] https://www.freebsd.org/cgi/man.cgi?query=hier&apropos=0&sektion=0&manpath=FreeBSD+6.1-RELEASE&format=html

> But like I say, who am I to suggest anything in unix ;=))
> Must have been too full of the Christmas cheer...

Enjoy the remaining holidays as well :)


  reply	other threads:[~2019-12-26 20:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 13:36 Adam Thompson
2019-12-25 13:47 ` Dominique Martinet
2019-12-25 14:05   ` Adam Thompson
2019-12-25 16:29     ` Dominique Martinet
2019-12-25 17:42       ` Geoff McLane
2019-12-26 18:43         ` Adam Thompson
2019-12-26 20:31           ` Geoff McLane
2019-12-26 20:51             ` Dominique Martinet [this message]
2019-12-27 15:58               ` alf.siciliano
2019-12-27 20:26                 ` Geoff McLane
2020-01-16 20:28                   ` Adam Thompson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191226205100.GA26919@nautica \
    --to=asmadeus@codewreck.org \
    --cc=alfix86@gmail.com \
    --cc=arthompson1990@gmail.com \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=ubuntu@geoffair.info \


* 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).