Please let us know when it appears on the GNU ftp site. The pkgsrc
entry is pointing at that, and I don't want to flip to github and back.
(I realize ftp upload credential fixing may not be super fast...)
"Adam Ciarcinski" writes:
> Module Name: pkgsrc
> Committed By: adam
> Date: Mon Apr 29 17:22:05 UTC 2019
>
> Modified Files:
> pkgsrc/misc/libcdio: Makefile PLIST distinfo
> Added Files:
> pkgsrc/misc/libcdio/patches: patch-configure
> patch-include_cdio++_iso9660.
Rocky Bernstein writes:
>> Thanks to all for paying attention to portability. The release builds
>> on NetBSD-8 under pkgsrc just fine, and I have just committed an update
>> to pkgsrc.
>
> Again this, is due to the careful work of both Edd and Thomas.
I saw that in your note, and I really did
Rocky Bernstein writes:
> See http://ftp.gnu.org/pub/gnu/libcdio/?C=M;O=D
>
> Thanks to everyone for the hop on this release and especially to Edd
> Barrett and Thomas Schmitt. This bulk of this release is work that they did.
[I disappeared from libcdio since it's something I wanted to help pack
(I'm a big paged out today and not really keeping up, but wanted to
comment quickly since I was asked.)
"Thomas Schmitt" writes:
> Edd Barrett wrote:
>> Is it important, though, to offer up both addressing modes for consumers
>> of libcdio? Or is it not exposed that way?
>> Put differently, if t
It turns out while I had actually built your branch and installed it to
/usr/local, I had a release in /usr/pkg. Sorry - I should be more
careful, but I'm not so used to flipping between pkg and hand built.
I ran "gmake check" on your branch, and there's still an mmc_read issue
like on master, bu
Edd Barrett writes:
> Thanks for testing.
Glad to help - I don't expect to be really digging in, but try to pop in
and help portability here and there.
[deleting lots of this when there's no reason for me to add anything]
> On Thu, Oct 25, 2018 at 08:28:56PM -0400, Greg Troxel
Rocky Bernstein writes:
> On Fri, Oct 26, 2018 at 12:40 PM Greg Troxel wrote:
>
>> How long should the libcdio-paranoia tests take?
>
> It took less than 41 seconds for me after having previousl compiled
> everything.
With the disc ejected, it didn't run "test
{I think my earlier report was confused due to multiple installed
versions; am retesting and will resend, but a query:)
How long should the libcdio-paranoia tests take?
Do they attempt to access a physical drive?
I rebuilt licdio-paranoia after purging a libcdio package, to ensure
that my system
Edd Barrett writes:
> Hi Greg,
>
> Thanks for getting back to us. I'm an OpenBSD developer trying to get
> the NetBSD driver to work for OpenBSD.
>
> On Fri, Oct 12, 2018 at 10:02:16PM -0400, Greg Troxel wrote:
>> 405: Option not supported by drive
>
> I&#x
(I have newly joined the list; Rocky appeared on a NetBSD list and asked
about libcdio on NetBSD. I'm been a NetBSD/pkgsrc developer for many
years.)
On a system running netbsd-7 amd64 (which is the old but supported
stable release), I built libcdio and libcdio-paranoia from their
respective git
11 matches
Mail list logo
