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

Hi Dominique, Adam,

What was I thinking... I am out of my depth... me, offer UNIX 
suggestion... ha, ha,...

But I do use cmake all-the-time, as my preferred cross-os build system 

And Adam, certainly agree with "it's almost always a good idea to keep
packaged and unpackaged software from playing with each other's installed

In a way that's why my build-me.sh is set to /NOT/ touch a dpkg install...

I started to look around at various other projects I can compile with 
find a lot of sometimes confusing, even contradictory... information...
and all that I find do often define their own man or doc install 
but generally each make it dependent on the root CMAKE_INSTALL_PREFIX...

So Dominique, it seems the fix you have is good... will get to testing 

But other questions popped up... like...

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

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>"...

But like I say, who am I to suggest anything in unix ;=))

Must have been too full of the Christmas cheer...

As state, your patch looks like a good start... sorry for the noise...

Regards, Geoff.

  reply	other threads:[~2019-12-26 20:31 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 [this message]
2019-12-26 20:51             ` Dominique Martinet
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=460ad829-de45-7788-f776-bcd37c65a0de@geoffair.info \
    --to=ubuntu@geoffair.info \
    --cc=arthompson1990@gmail.com \
    --cc=asmadeus@codewreck.org \
    --cc=edbrowse-dev@edbrowse.org \


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