The intended way to use autoconf-archive

--000000000000af414d05c9c747d4
Content-Type: text/plain; charset="UTF-8"

See https://github.com/madmurphy/not-autotools/issues/2 for context.

In brief, it's come to my attention that I can't tell, from the
autoconf-archive documentation as presented in git, what the intended usage
method is; namely whether:

1. Developers should install autoconf-archive like any other package,
depend on it like any other build dependency, and allow aclocal to copy
specific macros into their projects; or
2. Developers should simply copy the macros they want into their projects'
m4 directory.

Or both, or something else. I have been doing 2; the developer of
not-autotools claims (reasonably) that the intended way to use
autoconf-archive is 1.

It would be nice if there were a section in the autoconf-archive
documentation that settled this question.

-- 
https://rrt.sc3d.org

--000000000000af414d05c9c747d4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">See <a href=3D"https://github.com/madmu=
rphy/not-autotools/issues/2">https://github.com/madmurphy/not-autotools/iss=
ues/2</a> for context.</div><div class=3D"gmail_default" style=3D"font-fami=
ly:arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"=
>In brief, it&#39;s come to my attention that I can&#39;t tell, from the au=
toconf-archive documentation as presented in git, what the intended usage m=
ethod is; namely whether:</div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll">1. Developers should install autoconf-archive like any other package, d=
epend on it like any other build dependency, and allow aclocal to copy spec=
ific macros into their projects; or</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small">2. Developers s=
hould simply copy the macros they want into their projects&#39; m4 director=
y.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif;font-size:small">Or both, or somethi=
ng else. I have been doing 2; the developer of not-autotools claims (reason=
ably) that the intended way to use autoconf-archive is 1.</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,=
helvetica,sans-serif;font-size:small">It would be nice if there were a sect=
ion in the autoconf-archive documentation that settled this question.<br></=
div><br>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D=
"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><a href=3D"https:/=
/rrt.sc3d.org" target=3D"_blank">https://rrt.sc3d.org</a></div></div></div>=
</div></div>

--000000000000af414d05c9c747d4--