#11851: make pybtex an optional spkg
---------------------------------+------------------------------------------
Reporter: ranosch | Owner: tbd
Type: task | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: optional packages | Keywords: BibTeX citations
Work_issues: | Upstream: N/A
Reviewer: | Author: Niels Ranosch, Burcin Erocal
Merged: | Dependencies:
---------------------------------+------------------------------------------
Comment(by ranosch):
Thanks for looking into this!
Replying to [comment:1 jhpalmieri]:
> When I install the spkg on a Mac OS X box, I see this
> {{{
> Processing PyYAML-3.10.zip
> Running PyYAML-3.10/setup.py -q bdist_egg --dist-dir
/var/folders/JV/JVYCpshdHd4FFoThuUgD8k+++TI/-Tmp-/easy_install-
e_csNv/PyYAML-3.10/egg-dist-tmp-KAUGDh
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:2:18: error: yaml.h: No
such file or directory
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c: In function ‘main’:
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:5: error:
‘yaml_parser_t’ undeclared (first use in this function)
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:5: error: (Each
undeclared identifier is reported only once
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:5: error: for each
function it appears in.)
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:5: error: expected ‘;’
before ‘parser’
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:6: error:
‘yaml_emitter_t’ undeclared (first use in this function)
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:6: error: expected ‘;’
before ‘emitter’
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:8: warning: implicit
declaration of function ‘yaml_parser_initialize’
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:8: error: ‘parser’
undeclared (first use in this function)
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:9: warning: implicit
declaration of function ‘yaml_parser_delete’
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:11: warning: implicit
declaration of function ‘yaml_emitter_initialize’
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:11: error: ‘emitter’
undeclared (first use in this function)
> build/temp.macosx-10.6-i386-2.6/check_libyaml.c:12: warning: implicit
declaration of function ‘yaml_emitter_delete’
>
> libyaml is not found or a compiler error: forcing --without-libyaml
> (if libyaml is installed correctly, you may need to
> specify the option --include-dirs or uncomment and
> modify the parameter include_dirs in setup.cfg)
> zip_safe flag not set; analyzing archive contents...
> Adding PyYAML 3.10 to easy-install.pth file
> }}}
> Are these errors important? The installation proceeds, apparently
successfully, after this.
PyYAML Supports libYAML for speed reasons only, so you can ignore these
messages. But I removed libYAML support from the SPKG (I will update the
link soon), so that nobody gets confused.
>
> Second, would it be better to have three separate spkgs, one each for
pybtex, PyYAML, and pyparsing?
sagenb also includes its dependencies. It would be too much trouble to
maintain three different SPKGs.
>
> Third, should the file `patches/pybtex-doc_tree.patch.org` be deleted?
I see a reference to it in SPKG.txt, but why do we need it? It might be
better just to give the link to the original patch and then say that it
has been rebased. Rebasing is the only change, right?
We don't know, if the link will change or will be unavailable some day.
Burcin thought, it would probably be safer like this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11851#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
