Next | Query returned 18 messages, browsing 11 to 20 | previous

History of commit frequency

CVS Commit History:


   2017-12-16 23:53:15 by Pierre Pronchery | Files touched by this commit (2)
Log message:
Update devel/libusb-compat to version 0.1.6-rc2 (as 0.1.6rc2 here)

From the ChangeLog:

    tag the 0.1.6-rc1 release
    Add -no-undefined to LDFLAGS
    Add some missing definitions
    Use C99 standard fixed width integer types in usb.h
    Prevent libusb-1.0 library symbol clash
    Add a library destructor to handle cleaning up libusb.
    Revert "Link with -znodelete to disallow unloading"
    Revert "use atexit() to call libusb_exit()"
    Link with -znodelete to disallow unloading

Also changes the master site to GitHub.

Tested on NetBSD/amd64.

TODO: offer as an alternative to devel/libusb.
   2017-09-30 09:44:12 by Thomas Klausner | Files touched by this commit (1) | Package updated
Log message:
libusb-compat: update HOMEPAGE
   2016-03-26 08:53:32 by Richard PALO | Files touched by this commit (1)
Log message:
use POSIX typedefs for u_int*_t on SunOS
   2015-11-03 04:29:40 by Alistair G. Crooks | Files touched by this commit (1995)
Log message:
Add SHA512 digests for distfiles for devel category

Issues found with existing distfiles:
	distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
	distfiles/fortran-utils-1.1.tar.gz
	distfiles/ivykis-0.39.tar.gz
	distfiles/enum-1.11.tar.gz
	distfiles/pvs-3.2-libraries.tgz
	distfiles/pvs-3.2-linux.tgz
	distfiles/pvs-3.2-solaris.tgz
	distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.
   2014-11-24 13:53:19 by Makoto Fujiwara | Files touched by this commit (2) | Package updated
Log message:
update 0.1.4 to 0.1.5
---------------------
Date:   Mon May 20 17:34:02 2013 -0600
    libusb-compat-0.1.5

Date:   Mon May 20 17:33:43 2013 -0600
    Add bootstrap.sh and do not set debug mode by default.

Date:   Mon May 20 17:32:43 2013 -0600
    Replace the deprecated INCLUDES token with AM_CPPFLAGS in Makefile.am

Date:   Fri Aug 24 17:13:11 2012 -0400
    libusb.pc.in: Add missing Requires.private: libusb-1.0 so that
    pkg-config adds the libusb 1.0 library and dependencies when
    static linking.

Date:   Thu Apr 4 10:53:42 2013 -0600
    use atexit() to call libusb_exit()
    Fixes #130

Date:   Thu Apr 4 10:53:01 2013 -0600
    fix autoconf errors/warnings
    Fixes #161

Date:   Sun May 13 19:50:38 2012 +0800
    examples: Link only with ../libusb/libusb.la and not with -lusb

    Similar to libusb.git commit 93b0e09d53ed1d177631af9182378492481a790a
    http://git.libusb.org/?p=libusb.git;a=commitdiff;h=93b0e09d53ed1d177631af918

    Previous _LDFLAGS included both the freshly built libusb in ../libusb
    and -lusb, where libtool would usually resolve the latter to an
    already-installed libusb library in the system. The extra reference
    to a second libusb library may cause failures to build examples
    on some platforms and is wrong.

    Fixes #135.
   2012-10-31 12:19:55 by Aleksej Saushev | Files touched by this commit (1460)
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
   2012-05-31 13:58:12 by Thomas Klausner | Files touched by this commit (1)
Log message:
Depend on libusb1. Requested by upstream maintainer, Peter Stuge.
Bump PKGREVISION.
   2012-05-30 17:42:04 by Thomas Klausner | Files touched by this commit (4) | Imported package
Log message:
Initial import of libusb-compat-0.1.4.
Notes: depends on libusbx (we need a switch between the two)
Conflicts with libusb (we need a switch between the two)

libusb-compat-0.1 is a replacement for libusb-0.1. However, instead
of being an actual implementation, libusb-0.1 is more of a
compatibility layer (or wrapper) which just converts libusb-0.1
calls into their libusb-1.0 equivalents.

It aims to look, feel and behave exactly like libusb-0.1. As it is
a replacement, you cannot install it alongside libusb-0.1 on the
same system.

As the compatibility layer implements the exact same ABI and API,
no modifications to existing libusb-0.1-based applications are
needed. You do not even have to recompile them. This compatibility
layer is a drop-in replacement.


Next | Query returned 18 messages, browsing 11 to 20 | previous