CVS log for pkgsrc/net/py-suds/Attic/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / net / py-suds

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

py-suds: removed

Pullup ticket #5633 - requested by sevan
net/py-suds: build fix

Revisions pulled up:
- net/py-suds/Makefile                                          1.10

---
   Module Name:    pkgsrc
   Committed By:   wiz
   Date:           Fri Nov  3 19:40:31 UTC 2017

   Modified Files:
           pkgsrc/net/py-suds: Makefile

   Log Message:
   py-suds: replace dead HOMEPAGE with bad one at pypi

py-suds: replace dead HOMEPAGE with bad one at pypi

Add python-3.6 to incompatible versions.

Remove python33: adapt all packages that refer to it.

Switch to MASTER_SITES_PYPI.

Extend PYTHON_VERSIONS_INCOMPATIBLE to 35

Improve EGG_NAME default to work for packages with '-' in their name.
Remove now unnecessary overrides in various packages.

Mark packages that are not ready for python-3.3 also not ready for 3.4,
until proven otherwise.

Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE=  33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE=  33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.

Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.

Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.

Whitespace cleanups and other nits corrected, where necessary.

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

The Suds web services client is a lightweight soap-based client for python the
is licensed under LGPL. Basic features:
* No class generation
* Provides an object-like API.
* Reads wsdl at runtime for encoding/decoding
* Provides for the following SOAP (style) binding/encoding:
        - Document/Literal
        - RPC/Literal
        - RPC/Encoded (section 5)

The goal of suds is to present an RPC-like interface into soap-based web
services. This means that in most cases, users do not need to be concerned with
the complexities of the WSDL and referenced schemas. Regardless of which soap
message style is specified, the signature of the service methods remain the
same. Uses that do examine the WSDL will notice that even with the document
soap message style, the signature of each method resembles an RPC. The method
signature contains the contents of the document defined for the message instead
of the document itself.

Initial revision