Age | Commit message (Collapse) | Author | Files | Lines |
|
- Add LICENSE= x11
(upstream)
- Update cstream 2.7.5 to 3.1.1
3.1.1:
-----
-n <nbytes_to_stream> was not clear to use numbers > 2 GB. I didn't
notice since it worked fine if you used suffixes "K/M/G" as long as
the number was < 2 G. Sorry about that.
3.1.0:
------
O_DIRECT supported for input.
3.0.0:
------
IPV6 support for IPV6 day 2011.
The IPV6 support shouldn't break anything after hostname lookup
succeeds. Issues might be building on older platforms if I screwed up
the autoconf mechanism to not compile it in.
Having said that, assorted little code cleanups are in this release,
too. They shouldn't break anything but non-IPV6 things were touched.
Aftermath for 2.7.4 - 2.7.6:
----------------------------
ATTENTION:
I'm afraid that support for the '-B <size_of_buffer>' was clobbered in
2.7.4 or whereabouts. This one allowed you do have a reader do
multiple reads before the writer could write or vice versa.
Change reverted in 2.7.6.
2.7.4 and 2.7.5 do not have working -B.
2.8.0:
------
Support platforms that do not have open(2) with O_DIRECT.
Such as MacOS X.
2.7.6:
------
Revert 2.7.3 which broke -B
|
|
|
|
* NetBSD and general pkgsrc compatibility. Should get rid of the only
patch used in pkgsrc.
Changes 2.7.4:
* Print the message that we switch to normal from O_DIRECT only when
verbose > 0.
Changes 2.7.3:
* More c flags changes for more portability.
Changes 2.7.2:
* Fix compilation under Redhat-7.3.
Changes 2.7.1:
* Support for $CSTREAM_AUDIO_BITRATE.
|
|
|
|
|
|
Patch provided by Sergey Svishchev in private mail.
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
|
|
|
|
|
|
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
|
|
|
|
|