From: Alexis <surryhill@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>, Kristaps Dzonsons <kristaps@bsd.lv>
Cc: tech@mdocml.bsd.lv
Subject: Re: Allow configure variables to be set from environment
Date: Thu, 22 Jan 2015 08:32:31 +0100 [thread overview]
Message-ID: <20150122073231.GB1198@kei> (raw)
In-Reply-To: <20150122003556.GJ11796@iris.usta.de>
Hi Ingo, hi Kristaps,
> > Alexis, you said that the homebrew folks don't like patching
> > software. But there must be a facility to do so, no?
> > Shouldn't this patch be there, and not upstream?
Yes, there is a facility in Homebrew to apply custom patches.
From my experience the maintainers want those patches to
be very specific to Homebrew and encourage changes to be reported
and made upstream.
> I'm not quite sure that is better. If we have the patch in our
> tree, the risk that future code changes turn the patch into
> something that actually *does* become a security risk seems
> lower.
>
> Also note that mdocml.bsd.lv *is* the portable version of mandoc,
> so in the way, it is the right place to maintain such code - as
> long as it doesn't grow out of hand and obscure the code.
I agree with Ingo here.
Best,
Alexis
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2015-01-22 7:32 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
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 [this message]
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=20150122073231.GB1198@kei \
--to=surryhill@gmail.com \
--cc=kristaps@bsd.lv \
--cc=schwarze@usta.de \
--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).