Eli Schwartz added the comment:
Hmm, I've seen this accomplished elsewhere using m4_pattern_forbid, which would
make autoreconf fail with the following message:
```
configure.ac:17: error: possibly undefined macro: AX_C_FLOAT_WORDS_BIGENDIAN
If this token and others are legit
Eli Schwartz added the comment:
I started to look into this, but it seems like I'd need a bit of duplication to
handle byte compiling the installed files in two different Makefile targets.
The alternatives are templating, automake style, or GNU make'isms like the
$(call) fu
Change by Eli Schwartz :
--
nosy: +eschwartz
___
Python tracker
<https://bugs.python.org/issue40059>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Schwartz added the comment:
I filed issue43282 for this.
--
___
Python tracker
<https://bugs.python.org/issue27640>
___
___
Python-bugs-list mailin
New submission from Eli Schwartz :
cf. https://bugs.python.org/issue27640#msg386758
Carrying on from the addition of --disable-test-modules, I would find it
convenient to be able to still provide the tests, but install them separately.
The end result would be two distro packages, one slim
Eli Schwartz added the comment:
I have a slightly different interest in declining to install tests... Arch
Linux provides the tests as a split subpackage with currently some hacky shell
globbing to delete the tests after make install, then do a second libinstall
and delete everything but
Eli Schwartz added the comment:
Interestingly enough, the final accepted patch (and the 2010 one) also fixes a
bug where gettext.install(..., names='ngettext') would incorrectly work, in
violation of the documentation.
I think it would also incorrectly install 'gettext'
Change by Eli Schwartz :
--
nosy: +eschwartz
___
Python tracker
<https://bugs.python.org/issue1724822>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Eli Schwartz :
--
nosy: +eschwartz
___
Python tracker
<https://bugs.python.org/issue34022>
___
___
Python-bugs-list mailing list
Unsubscribe:
Eli Schwartz added the comment:
Note the last line, which shows that the testsuite itself is executed using
xvfb-run.
The archlinux32 build script is based off the original PKGBUILD for archlinux:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/python2
xvfb
Eli Schwartz added the comment:
So, a couple of things.
It seems to me, that properly supporting SOURCE_DATE_EPOCH means using exactly
that and nothing else. To that end, I'm not entirely sure why things like
--clamp-mtime even exist, as the original timestamp of a source file doesn
11 matches
Mail list logo