Hello community,

here is the log from the commit of package python3-recommonmark for 
openSUSE:Factory checked in at 2016-06-02 09:36:55
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python3-recommonmark (Old)
 and      /work/SRC/openSUSE:Factory/.python3-recommonmark.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python3-recommonmark"

Changes:
--------
New Changes file:

--- /dev/null   2016-04-07 01:36:33.300037506 +0200
+++ 
/work/SRC/openSUSE:Factory/.python3-recommonmark.new/python3-recommonmark.changes
   2016-06-02 09:36:57.000000000 +0200
@@ -0,0 +1,18 @@
+-------------------------------------------------------------------
+Thu May 19 15:16:07 UTC 2016 - [email protected]
+
+- Update to version 0.4.0
+  * No upstream changelog
+
+-------------------------------------------------------------------
+Sun May  8 07:15:20 UTC 2016 - [email protected]
+
+- specfile:
+  * updated source url to files.pythonhosted.org
+
+
+-------------------------------------------------------------------
+Thu Dec 10 13:07:36 UTC 2015 - [email protected]
+
+- Initial packaging on obs 
+

New:
----
  README.md
  license.md
  python3-recommonmark.changes
  python3-recommonmark.spec
  recommonmark-0.4.0.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python3-recommonmark.spec ++++++
#
# spec file for package python3-CommonMark
#
# Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#


Name:           python3-recommonmark
Version:        0.4.0
Release:        0
Summary:        Python docutils-compatibility bridge to CommonMark
License:        MIT
Group:          Development/Languages/Python
Url:            https://github.com/rtfd/recommonmark
Source0:        
https://files.pythonhosted.org/packages/source/r/recommonmark/recommonmark-%{version}.tar.gz
Source1:        
https://raw.githubusercontent.com/rtfd/recommonmark/master/license.md
Source2:        
https://raw.githubusercontent.com/rtfd/recommonmark/master/README.md
BuildRequires:  fdupes
BuildRequires:  python3
BuildRequires:  python3-devel
BuildRequires:  python3-setuptools
BuildRequires:  python3-docutils
BuildRequires:  python3-CommonMark
Requires:       python3-docutils
Requires:       python3-CommonMark
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildArch:      noarch
Provides:       python3-reCommonMark = %{version}
Obsoletes:      python3-reCommonMark < %{version}

%description
A python docutils-compatibility bridge to CommonMark.

This allows you to write CommonMark inside of Docutils & Sphinx projects.

Documentation is available on Read the Docs:
http://recommonmark.readthedocs.org

%prep
%setup -q -n recommonmark-%{version}
# Remove upstream's egg-info
rm -rf %{pypi_name}.egg-info
#Add missing license and readme
cp -a %{SOURCE1} .
cp -a %{SOURCE2} .
# find and remove unneeded shebangs
find recommonmark -name "*.py" | xargs sed -i '1 {/^#!/ d}'
# correct shebang
sed -i 's@^#!/usr/bin/python2@#!/usr/bin/python3@' recommonmark/scripts.py

%build
python3 setup.py build

%install
python3 setup.py install --prefix=%{_prefix} --root=%{buildroot}
%fdupes %{buildroot}%{_prefix}

# Prepare for update-alternatives usage
mkdir -p %{buildroot}%{_sysconfdir}/alternatives
for B in cm2html cm2latex cm2man cm2pseudoxml cm2xetex cm2xml; do
    mv %{buildroot}%{_bindir}/${B} %{buildroot}%{_bindir}/${B}-%{py3_ver}
    ln -s -f %{_sysconfdir}/alternatives/${B} %{buildroot}%{_bindir}/${B}
    # create a dummy target for /etc/alternatives/${B}
    touch %{buildroot}%{_sysconfdir}/alternatives/${B}
done

%post
%_sbindir/update-alternatives \
   --install %{_bindir}/cm2man cm2man %{_bindir}/cm2man-%{py3_ver} 30 \
   --slave %{_bindir}/cm2latex cm2latex %{_bindir}/cm2latex-%{py3_ver}  \
   --slave %{_bindir}/cm2xetex cm2xetex %{_bindir}/cm2xetex-%{py3_ver}  \
   --slave %{_bindir}/cm2pseudoxml cm2pseudoxml 
%{_bindir}/cm2pseudoxml-%{py3_ver}  \
   --slave %{_bindir}/cm2html cm2html %{_bindir}/cm2html-%{py3_ver}  \
   --slave %{_bindir}/cm2xml cm2xml %{_bindir}/cm2xml-%{py3_ver}

%postun
if [ $1 -eq 0 ] ; then
    "%_sbindir/update-alternatives" --remove cm2man %{_bindir}/cm2man-%{py3_ver}
fi

%files
%defattr(-,root,root,-)
%doc README.md license.md
%{_bindir}/cm2html
%{_bindir}/cm2latex
%{_bindir}/cm2man
%{_bindir}/cm2pseudoxml
%{_bindir}/cm2xetex
%{_bindir}/cm2xml
%{_bindir}/cm2html-%{py3_ver}
%{_bindir}/cm2latex-%{py3_ver}
%{_bindir}/cm2man-%{py3_ver}
%{_bindir}/cm2pseudoxml-%{py3_ver}
%{_bindir}/cm2xetex-%{py3_ver}
%{_bindir}/cm2xml-%{py3_ver}
%ghost %{_sysconfdir}/alternatives/cm2html
%ghost %{_sysconfdir}/alternatives/cm2latex
%ghost %{_sysconfdir}/alternatives/cm2man
%ghost %{_sysconfdir}/alternatives/cm2pseudoxml
%ghost %{_sysconfdir}/alternatives/cm2xetex
%ghost %{_sysconfdir}/alternatives/cm2xml
%{python3_sitelib}/recommonmark/
%{python3_sitelib}/recommonmark-%{version}-py*.egg-info

%changelog
++++++ README.md ++++++
# recommonmark

A `docutils`-compatibility bridge to [CommonMark][cm].

This allows you to write CommonMark inside of Docutils & Sphinx projects.

Documentation is available on Read the Docs: 
<http://recommonmark.readthedocs.org>

Contents
--------
* [API Reference](api_ref.md)
* [AutoStructify Component](auto_structify.md)

## Getting Started

To use `recommonmark` inside of Sphinx only takes 2 steps. 
First you install it:

```
pip install recommonmark 
```

Then add this to your Sphinx conf.py:

```
from recommonmark.parser import CommonMarkParser

source_parsers = {
    '.md': CommonMarkParser,
}

source_suffix = ['.rst', '.md']
```

This allows you to write both `.md` and `.rst` files inside of the same project.

### AutoStructify

To use the advanced markdown to rst transformations you must add 
`AutoStructify` to your Sphinx conf.py.

```python
# At top on conf.py (with other import statements)
import recommonmark
from recommonmark.transform import AutoStructify

# At the bottom of conf.py
def setup(app):
    app.add_config_value('recommonmark_config', {
            'url_resolver': lambda url: github_doc_root + url,
            'auto_toc_tree_section': 'Contents',
            }, True)
    app.add_transform(AutoStructify)
```

See https://github.com/rtfd/recommonmark/blob/master/docs/conf.py for a full 
example.

AutoStructify comes with the following options. See 
http://recommonmark.readthedocs.org/en/latest/auto_structify.html for more 
information about the specific features.

* __enable_auto_toc_tree__: enable the Auto Toc Tree feature.
* __auto_toc_tree_section__: when True, Auto Toc Tree will only be enabled on 
section that matches the title.
* __enable_auto_doc_ref__: enable the Auto Doc Ref feature.
* __enable_math__: enable the Math Formula feature.
* __enable_inline_math__: enable the Inline Math feature.
* __enable_eval_rst__: enable the evaluate embedded reStructuredText feature.
* __url_resolver__: a function that maps a existing relative position in the 
document to a http link

## Development

You can run the tests by running `tox` in the top-level of the project.

We are working to expand test coverage,
but this will at least test basic Python 2 and 3 compatability.

## Why a bridge?

Many python tools (mostly for documentation creation) rely on `docutils`.
But [docutils][dc] only supports a ReStructuredText syntax.

For instance [this issue][sphinx-issue] and [this StackOverflow
question][so-question] show that there is an interest in allowing `docutils`
to use markdown as an alternative syntax.

## Why another bridge to docutils?

recommonmark uses the [python implementation][pcm] of [CommonMark][cm] while
[remarkdown][rmd] implements a stand-alone parser leveraging [parsley][prs].

Both output a [`docutils` document tree][dc] and provide scripts
that leverage `docutils` for generation of different types of documents.

## Acknowledgement

recommonmark is mainly derived from [remarkdown][rmd] by Steve Genoud and
leverages the python CommonMark implementation.

It was originally created by [Luca Barbato][lu-zero],
and is now maintained in the Read the Docs (rtfd) GitHub organization.

[cm]: http://commonmark.org
[pcm]: https://github.com/rtfd/CommonMark-py
[rmd]: https://github.com/sgenoud/remarkdown
[prs]: https://github.com/python-parsley/parsley
[lu-zero]: https://github.com/lu-zero

[dc]: http://docutils.sourceforge.net/docs/ref/doctree.html
[sphinx-issue]: 
https://bitbucket.org/birkenfeld/sphinx/issue/825/markdown-capable-sphinx
[so-question]: 
http://stackoverflow.com/questions/2471804/using-sphinx-with-markdown-instead-of-rst
++++++ license.md ++++++
The MIT License (MIT)

Copyright (c) 2014 Steve Genoud

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Reply via email to