[3481] in BarnOwl Developers
Re: [barnowl] Update and make configurable the default format (#136)
daemon@ATHENA.MIT.EDU (Jason Gross)
Sun Jun 9 22:07:05 2013
Date: Sun, 09 Jun 2013 19:07:01 -0700
From: Jason Gross <notifications@github.com>
Reply-To: barnowl/barnowl <reply+i-15055026-2049c87dc71753ba41b2922153aac251ad51a146-4475081@reply.github.com>
To: barnowl/barnowl <barnowl@noreply.github.com>
Cc: barnowl-dev email-only account <barnowl-dev@mit.edu>
In-Reply-To: <barnowl/barnowl/pull/136@github.com>
----==_mimepart_51b534c5c6790_7274583dd851241
Date: Sun, 09 Jun 2013 19:07:01 -0700
Mime-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-ID: <51b534c5c86be_7274583dd851342@worker5.rs.github.com.mail>
Ok, that sounds reasonable to me. I'm fine with this being merged as-is.=
-Jason
On Jun 9, 2013 9:37 PM, "barnowl-dev email-only account" <
notifications@github.com> wrote:
> Jason Gross <notifications@github.com> wrote:
>
> >I'm curious what jhutz has to say about why. (My reading of his
> >zephyrs was that autoconf doesn't give many options to configure thing=
s
> >at build time. But `--with-*` and `--enable-*` behave identically,
> >except for whether they list things as packages or features, AIUI.
>
> In the autoconf mindset, with and enable are both wrong for this. There=
is
> no right way to do this. Given that, '--with-default-fomat' sounds bett=
er,
> as it usually does for this sort of thing, so I tend to favor it. I've =
seen
> both used.
>
> In any case, a good part of why is avoiding bikeshedding.
>
> --Jeff
>
> =E2=80=94
> Reply to this email directly or view it on GitHub<https://github.com/ba=
rnowl/barnowl/pull/136#issuecomment-19177839>
> .
>
---
Reply to this email directly or view it on GitHub:
https://github.com/barnowl/barnowl/pull/136#issuecomment-19178289=
----==_mimepart_51b534c5c6790_7274583dd851241
Date: Sun, 09 Jun 2013 19:07:01 -0700
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-ID: <51b534c5c91ac_7274583dd8514d2@worker5.rs.github.com.mail>
Ok, that sounds reasonable to me. I'm fine with this being merged as=
-is.
<br>
<br>
-Jason
<br>
On Jun 9, 2013 9:37 PM, "barnowl-dev email-only account" <
<br>
notifications@github.com> wrote:
<br>
<br>
> Jason Gross <notifications@github.com> wrote:
<br>
>
<br>
> >I'm curious what jhutz has to say about why. (My reading of =
his
<br>
> >zephyrs was that autoconf doesn't give many options to confi=
gure things
<br>
> >at build time. But `--with-*` and `--enable-*` behave identicall=
y,
<br>
> >except for whether they list things as packages or features, AIU=
I.
<br>
>
<br>
> In the autoconf mindset, with and enable are both wrong for this. Th=
ere is
<br>
> no right way to do this. Given that, '--with-default-fomat' =
sounds better,
<br>
> as it usually does for this sort of thing, so I tend to favor it. I&=
#39;ve seen
<br>
> both used.
<br>
>
<br>
> In any case, a good part of why is avoiding bikeshedding.
<br>
>
<br>
> --Jeff
<br>
>
<br>
> =E2=80=94
<br>
> Reply to this email directly or view it on GitHub<https://github.=
com/barnowl/barnowl/pull/136#issuecomment-19177839>
<br>
> .
<br>
>
<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br>Reply to this email directly or <a href=3D'https://github.com/ba=
rnowl/barnowl/pull/136#issuecomment-19178289'>view it on GitHub</a>.<img =
src=3D'https://github.com/notifications/beacon/JJk3yKd0u6qAmPAmJXdf99lbpe=
DhTmH4RRsFgUZVxsWHjq7cATHmpnpxZ6OYAZvE.gif' height=3D'1' width=3D'1'></p>=
----==_mimepart_51b534c5c6790_7274583dd851241--
