tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Alexis <surryhill@gmail.com>
Cc: tech@mdocml.bsd.lv
Subject: Re: Allow configure variables to be set from environment
Date: Sat, 17 Jan 2015 02:07:06 +0100	[thread overview]
Message-ID: <20150117010706.GH9772@iris.usta.de> (raw)
In-Reply-To: <20150116215840.GF740@kei.fritz.box>

Hi Alexis,

Alexis wrote on Fri, Jan 16, 2015 at 10:58:40PM +0100:

> I have written a Hombrew

Urgs.  That symlinking business is just ridiculous, especially
when it comes to manuals.  I strongly advise against using homebrew,
it just doesn't work.  For example, mandoc(1) denies following
symlinks outside the respective manual tree for security reasons.

I admit i don't speak ruby, but your script looks wrong.
You have to run "make" as non-root and "make install" as root.
I don't see how your script is doing that.

> formula for mdocml, so OS X users can install and use mdocml.

Why is the OS X ecosystem *that* fragmented?  Now we have three OS
X ports.  One completely outdated (at Macports), one using a package
manager that is broken by design, and the best one - using pkgsrc -
maintained externally by NetBSD.

Having one official port provided officially by the operating system
developers would clearly be preferable.  Can you try to talk them
into that, maybe providing code to them that they just have to verify
and commit?  That would really be helpful!

> In order to adhere to the best practices in Homebrew I propose
> the diff below, so that certain variables like PREFIX,
> BINDIR, etc. can be changed by simply setting them in the
> environment

I intentionally do not trust the environment, it might contain
god knows what I would never dream of somebody might put there
and the user would never dream of that i might look at.
I strongly resent environment variables in general.  On the
one hand, we are all into object oriented programming, on the
other hand, people make stuff so global that it's not even
clear which applications it applies to.

When building *one* program, you certainly don't need to make
your settings completely global, or feed completely global stuff
into it.

> and without needing to edit configure, e.g.:
>   % PREFIX=/opt/local ./configure

You shouldn't edit configure, the recommended way is to
put your settings into configure.local, see INSTALL and
configure.local.example for instructions and examples.

> If there is another way to achieve this please let me know.
> 
> 9 http://brew.sh - a package manager for OS X
> 2 https://github.com/afh/homebrew/blob/pull/mdocml/Library/Formula/mdocml.rb

For now, i have linked the pull request from

  http://mdocml.bsd.lv/ports.html
  http://mdocml.bsd.lv/porthistory.html

In case it gets merged to

  https://github.com/Homebrew/homebrew

please tell me to update the link.

Thanks,
  Ingo


> Index: configure
> ===================================================================
> RCS file: /cvs/mdocml/configure,v
> retrieving revision 1.17
> diff -r1.17 configure
> 66,72c66,72
> < PREFIX="/usr/local"
> < BINDIR=
> < SBINDIR=
> < INCLUDEDIR=
> < LIBDIR=
> < MANDIR=
> < EXAMPLEDIR=
> ---
> > PREFIX="${PREFIX:-/usr/local}"
> > BINDIR=${BINDIR}
> > SBINDIR=${SBINDIR}
> > INCLUDEDIR=${INCLUDEDIR}
> > LIBDIR=${LIBDIR}
> > MANDIR=${MANDIR}
> > EXAMPLEDIR=${EXAMPLEDIR}
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2015-01-17  1:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sfid-H20150116-225859-+021.89-1@spamfilter.osbf.lua>
2015-01-16 21:58 ` Alexis
2015-01-16 23:32   ` Thomas Klausner
2015-01-17  1:31     ` Ingo Schwarze
2015-01-17  1:07   ` Ingo Schwarze [this message]
2015-01-17 20:10     ` Kristaps Dzonsons
2015-01-18  3:33       ` Ingo Schwarze
2015-01-20 15:15         ` Alexis
2015-01-21 23:05           ` Ingo Schwarze
2015-01-22  0:21             ` Kristaps Dzonsons
2015-01-22  0:35               ` Ingo Schwarze
2015-01-22  7:32                 ` Alexis
2015-01-22  7:26             ` Alexis
2015-01-23 22:05               ` Ingo Schwarze
2015-01-20 15:19     ` Alexis
2015-01-21 21:07       ` Ingo Schwarze

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=20150117010706.GH9772@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=surryhill@gmail.com \
    --cc=tech@mdocml.bsd.lv \
    /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).