Re: [Libcdio-devel] removal of include/cdio/cdio_config.h

On Sun, Jan 29, 2012 at 10:36 AM, Pete Batard wrote: > As per previous posts, the -pbatard branch now has had the requirement for > cdio_config.h (and cdio_unconfig.h) removed [1]. > Removing the requirement cdio_config.h is probably okay. However removing it ultimately from the distribution is

Re: [Libcdio-devel] Fix mmc_ll_cmds.c for use with MSVC compilers

On Sun, Jan 29, 2012 at 12:46 PM, Pete Batard wrote: > This one is fairly straightforward, but I'll sent it to the list > nonetheless. > > The issue here is that when not compiling a C++, MSVC compilers do not > accept variables to be defined after code, and the MMC_CMD_SETUP() macro > does defin

Re: [Libcdio-devel] modifications of ISO9660 and UDF headers for MSVC

On Sun, Jan 29, 2012 at 12:39 PM, Pete Batard wrote: > Two additional patches that modify the ISO9660 and UDF headers for MSVC > usage. > > The most controversial has to be the ISO9660 as MSVC simply cannot use a > zero sized array, even at the end of a struct, if that struct is going to > be inc

Re: [Libcdio-devel] removal of include/cdio/cdio_config.h

On Mon, Jan 30, 2012 at 8:47 AM, Pete Batard wrote: > On 2012.01.30 02:22, Rocky Bernstein wrote: > >> Removing the requirement cdio_config.h is probably okay. However removing >> it ultimately from the distribution is a little bit different. >> >> The file serv

Re: [Libcdio-devel] Fix mmc_ll_cmds.c for use with MSVC compilers

On Mon, Jan 30, 2012 at 9:53 AM, Robert Fuller wrote: > On Sun, Jan 29, 2012 at 9:24 PM, Rocky Bernstein wrote: > > On Sun, Jan 29, 2012 at 12:46 PM, Pete Batard wrote: > > > >> This one is fairly straightforward, but I'll sent it to the list > >> nonethe

Re: [Libcdio-devel] Fix mmc_ll_cmds.c for use with MSVC compilers

On Mon, Jan 30, 2012 at 11:47 AM, Pete Batard wrote: > On 2012.01.30 14:53, Robert Fuller wrote: > >> This brings up an important point. MSVC >> does not support C99 and Microsoft has no stated plans to support it. >> > > Unfortunately, that's absolutely true. That's also why trying to reuse > C

Re: [Libcdio-devel] Fix mmc_ll_cmds.c for use with MSVC compilers

support for these has OS's wained, it is because the people who were interested in them have lost interest. I'm not expressing this as a good or bad thing -- just they way things are. On Mon, Jan 30, 2012 at 9:45 PM, Rocky Bernstein wrote: > > > On Mon, Jan 30, 2012 at 11:47 AM,

Re: [Libcdio-devel] Fix mmc_ll_cmds.c for use with MSVC compilers

On Tue, Jan 31, 2012 at 11:22 AM, Pete Batard wrote: > On 2012.01.31 02:50, Rocky Bernstein wrote: > >> I meant to add one other small point which I think should be worth >> mentioning. >> >> In a project like libcdio the extent of its portability is determined >

Re: [Libcdio-devel] CD-TEXT documentation

On Sat, Feb 4, 2012 at 6:27 AM, Thomas Schmitt wrote: > Hi, > > now that i have released libburn and cdrskin with CD-TEXT features, > i want to contribute to the libcdio docs about that topic. > Many thanks! Independent of libcdio, public CD Text documentation at an implementation level is much

Re: [Libcdio-devel] CD-TEXT documentation

I have made a very quick and rough markup of cdtext.txt and it is now in git in the main branch. >From markup and the editorial side I think a bit more is needed. I've removed some of the libburn-specific things. It would be nice if we could separate this out in a way that the same subset info co

Re: [Libcdio-devel] CD-TEXT documentation

On Sat, Feb 4, 2012 at 11:25 AM, Leon Merten Lohse wrote: > Thank you Thomas! > > On Sat, Feb 04, 2012 at 10:06:41AM -0500, Rocky Bernstein wrote: > > > doc/libcdio.texi: > > > > > > Some of its aspects go beyond my own CD knowledge. > > > Nev

Re: [Libcdio-devel] removal of include/cdio/cdio_config.h

On Mon, Jan 30, 2012 at 9:36 PM, Rocky Bernstein wrote: > On Mon, Jan 30, 2012 at 8:47 AM, Pete Batard wrote: > >> On 2012.01.30 02:22, Rocky Bernstein wrote: >> >>> Removing the requirement cdio_config.h is probably okay. However removing >>> it ultimately f

Re: [Libcdio-devel] CD-TEXT documentation

I have made edits to libcdio libcdio.texi and cd-text.texi taking into account what you report below. If this is not sufficient let me know. http://jbum.com/cdg_revealed.html gives me the impression that CD+G uses the R-W sub code in contrast to the program area that you report that CD Text uses e

Re: [Libcdio-devel] CD-TEXT documentation

On Sun, Feb 5, 2012 at 12:23 PM, Thomas Schmitt wrote: > Hi, > > > http://jbum.com/cdg_revealed.html > > Very interesting. (Very very pre-MMC, too.) > > The graphics protocol reminds me of my first self-implemented pixel > graphics > on a VIC-20. > It has nothing to do with CD-TEXT, except that i

Re: [Libcdio-devel] CD-TEXT documentation

On Mon, Feb 6, 2012 at 8:38 AM, Thomas Schmitt wrote: > Hi, > > > One small thing I've noticed is that there is mention to mm5r03.pdf > > and that is not in the references. > > Good point. I have looked up the equivalent spots in MMC-3: > > mmc5r03c.pdf, table 490 TOC Track Descriptor Format, Q S

Re: [Libcdio-devel] CD-TEXT documentation

On Mon, Feb 6, 2012 at 10:42 AM, Thomas Schmitt wrote: > Hi, > > > xor 0x is exactly the same things a mod 2**16. You must be talking > > about something else. > > I understand it like this: > xor 0x inverts the lowest 16 bits. > Ooops -- yes, you are correct! But again that's the point

Re: [Libcdio-devel] CD-TEXT documentation

With the last revision in git the document is now up at http://www.gnu.org/software/libcdio/cd-text-format.html I expect there will be more changes and probably more mistakes to be found. Thanks, everyone! On Mon, Feb 6, 2012 at 11:34 AM, Thomas Schmitt wrote: > Hi, > > > If nothing else it wo

Re: [Libcdio-devel] CD-TEXT documentation

On Wed, Feb 8, 2012 at 5:10 AM, Thomas Schmitt wrote: > Hi, > > > http://www.gnu.org/software/libcdio/cd-text-format.html > > It looks so shiny as html. :)) > Personally, I think the PDF formatting is nicer. But HTML is what the Internet uses. > > - > > 1.2: > > One should introduce the "S

Re: [Libcdio-devel] CD-TEXT documentation

On Wed, Feb 8, 2012 at 8:01 AM, Thomas Schmitt wrote: > Hi, > > > Funny you should bring that up. After registering with Sony at I can't > find > > cdtext.zip on http://www.sonydadc.com > > We had to retrieve it from the Wayback machine. > Well, I registered then with Sony for no reason at all.

Re: [Libcdio-devel] CD-TEXT documentation

On Wed, Feb 8, 2012 at 12:17 PM, Thomas Schmitt wrote: > Hi, > > > I had looked on the Wayback as well and couldn't find it. Do you have an > > exact URL? > > My own endeavor is described in the archives > http://lists.gnu.org/archive/html/libcdio-devel/2011-11/msg00030.html > you then reported

Re: [Libcdio-devel] CD-TEXT documentation

am going to update the CD-Text libcdio api documentation once I am done > fixing it. > Thanks. I'd appreciate it. I'm interested in having good documentation out there on this aspect, not interested writing it or spending back and forth time on the mailing list. You guys are more o

Re: [Libcdio-devel] CD-TEXT documentation

On Thu, Feb 9, 2012 at 3:09 AM, Thomas Schmitt wrote: > Hi, > > > It get the impression that drafts, or at least some, of them were > > distributed for public review. And that's why many are still around. > > One can still find them if one searches intensly enough. > If this is the best that can

Re: [Libcdio-devel] [PATCH 0/5] Integration of libcdio-pbatard changes

On Fri, Feb 10, 2012 at 2:34 PM, Pete Batard wrote: > With libcdio-pbatard now complete in terms of fixes and features, I am in > a position to push for the changes to be integrated into mainline at last. > Great! > > As previously indicated I have created a new pbatard-integration branch > de

Re: [Libcdio-devel] [PATCH 2/5] Add extract ISO/UDF example

using libiso9660 to extract a file from an > ISO-9660 image. > > diff --git a/example/extract.c b/example/extract.c > new file mode 100644 > index 000..2d9a90c > --- /dev/null > +++ b/example/extract.c > @@ -0,0 +1,311 @@ > +/* > + Copyright (C) 2012 Pet

Re: [Libcdio-devel] [PATCH 2/5] Add extract ISO/UDF example

On Sun, Feb 12, 2012 at 7:36 PM, Pete Batard wrote: > On 2012.02.12 14:53, Rocky Bernstein wrote: > >> I get a failure running the check_udf.sh created by this patch: >> > > Well, there are some UDF patches missing from -pbatard, so the test is not > supposed to work

Re: [Libcdio-devel] [PATCH 2/5] Add extract ISO/UDF example

me estimate on this other than before the next release. On Mon, Feb 13, 2012 at 7:31 AM, Pete Batard wrote: > On 2012.02.13 07:33, Rocky Bernstein wrote: > >> Although I said in test-driven development, advocates suggest writing >> tests >> first, so tests start out broken,

[Libcdio-devel] RFC: Two releases or one?

There have a few larger unrelated changes that taken place and I would like to solicit opinions on whether we should have one release with all of the changes or two? The changes are * CD-Text completion (some incompatibility) * UDF improvement and header reworking for Microsoft OS's * Removal of

Re: [Libcdio-devel] RFC: Two releases or one?

On Mon, Feb 20, 2012 at 5:23 PM, Nicolas Boullis wrote: > Hi, > > On Mon, Feb 20, 2012 at 07:45:15AM -0500, Rocky Bernstein wrote: > > There have a few larger unrelated changes that taken place and I would > like > > to solicit opinions on whether we should have one

Re: [Libcdio-devel] RFC: Two releases or one?

On Mon, Feb 20, 2012 at 9:45 AM, Pete Batard wrote: > On 2012.02.20 12:45, Rocky Bernstein wrote: > >> There have a few larger unrelated changes that taken place and I would >> like >> to solicit opinions on whether we should have one release with all of the >> cha

Re: [Libcdio-devel] RFC: Two releases or one?

On Wed, Feb 22, 2012 at 7:30 AM, Pete Batard wrote: > On 2012.02.21 12:51, Rocky Bernstein wrote: > >> Since no other comments, looks like we'll go for one release with >> everything. >> > > Great. > > As previously indicated, I'd still prefer to p

Re: [Libcdio-devel] RFC: Two releases or one?

changes (language selection) this weekend. > This way it is going to be a single rather big incompatible change. > > If you have objections, I can try to write a workaround but it is not > going to be pretty and will not help making the api easier. > > Regards > Leon >

Re: [Libcdio-devel] CD-Text API changes

On Sat, Feb 25, 2012 at 5:57 PM, Leon Merten Lohse wrote: > Hi, > > I would like to present you the new CD-Text API for further discussion. > With version 0.82 there was: > cdtext.h: > const char *cdtext_field2str (cdtext_field_t i); > void cdtext_init (cdtext_t *cdtext); > void cdtext_destroy

Re: [Libcdio-devel] CD-Text API changes

On Mon, Feb 27, 2012 at 3:26 PM, Leon Merten Lohse wrote: > On Sun, Feb 26, 2012 at 06:23:32PM -0500, Rocky Bernstein wrote: > > Thank you very much for this write up. I really appreciate it. > > > > Some thoughts with regards to the questions I asked and the concerns >

Re: [Libcdio-devel] CD-Text API changes

On Mon, Feb 27, 2012 at 3:26 PM, Leon Merten Lohse wrote: > On Sun, Feb 26, 2012 at 06:23:32PM -0500, Rocky Bernstein wrote: > > Thank you very much for this write up. I really appreciate it. > > > > Some thoughts with regards to the questions I asked and the concerns >

[Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

Kind people - Pete Batard's patches have now been merged into the git master branch. Pete: it is possible there are some small residual changes I've missed. If that is the case send patches and we'll take care of. I've tested the changes using "make distcheck" on GNU/Linux, cygwin , Solaris and

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Sun, Mar 4, 2012 at 8:45 PM, Pete Batard wrote: > On 2012.03.04 22:53, Rocky Bernstein wrote: > >> Pete Batard's patches have now been merged into the git master branch. >> > > Wow, thanks! I've been trying to find time to get things going with the > i

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Sun, Mar 4, 2012 at 8:45 PM, Pete Batard wrote: > On 2012.03.04 22:53, Rocky Bernstein wrote: > >> Pete Batard's patches have now been merged into the git master branch. >> > > Wow, thanks! I've been trying to find time to get things going with the > i

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Mon, Mar 5, 2012 at 10:12 AM, Pete Batard wrote: > On 2012.03.05 03:41, Rocky Bernstein wrote: > >> On another note, I see there are still paranoia related files in >>> src/cd-paranoia/ as well as a test/testparanoia.c. Shouldn't these be >>> removed as wel

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Mon, Mar 5, 2012 at 8:25 PM, Pete Batard wrote: > OK, pbatard-integration2 should now be pretty much in line with -pbatard, > short of additional patches that will be required for MSVC project files > (but those are fairly independent). > I have tested these on the various platforms and every

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Tue, Mar 6, 2012 at 8:44 PM, Pete Batard wrote: > Getting into the final pieces of the puzzle now, with 4 more commits in > integration2. > Ok. Thanks for plugging away. > > The first one is yet another round of paranoia/unconfig removal (will we > ever see the end of those?). > Ok. Will me

[Libcdio-devel] CD-Text Multi-language from greenleon

Leon Merten Lohse Multi-language CD-Text improvements have just been added to the main/master branch of git. From Leon: * All the api changes I wrote about. * A lot of moving and renaming inside the CD-Text sources. * A more or less rewritten parsing routine that does not rely on the PACKED pragma

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Fri, Mar 9, 2012 at 6:43 AM, Pete Batard wrote: > On 2012.03.09 02:09, Rocky Bernstein wrote: > >> We also modify the win32 cdrom driver files so that >>> 1. It works with Visual Studio >>> 2. It doesn't require end user applications to link with any

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

ow. If I've missed addressing any concerns, just ask. On Sun, Mar 11, 2012 at 7:40 PM, Pete Batard wrote: > On 2012.03.11 01:14, Rocky Bernstein wrote: > >> In all cases, considering that we only use 2 calls for winmm, we might as >>> well remove the need to specify

[Libcdio-devel] RFC: Savannah issue bug #35745

A patch was recently submitted: https://savannah.gnu.org/bugs/?35745 Any comments on this?

Re: [Libcdio-devel] CD-Text API changes

On Mon, Mar 12, 2012 at 3:48 AM, leon wrote: > On 2012-03-12 01:20, Nicolas Boullis wrote: > >> I am a bit curious: why does cdtext_select_language take a "const char *" >> parameter for the language, while cdtext_get_language and >> cdtext_languages_available return cdtext_lang_t value(s)? Would

Re: [Libcdio-devel] CD-Text API changes

On Mon, Mar 12, 2012 at 12:48 PM, leon wrote: > On 2012-03-12 12:12, Nicolas Boullis wrote: > > First I thought it to be easier this way. But the more I think about >>> it, keeping localization in mind, the less I like it. Any other >>> opinions? >>> >> >> Sorry, I don't understand what you mean

Re: [Libcdio-devel] RFC: Savannah issue bug #35745

On Mon, Mar 12, 2012 at 5:09 AM, Nicolas Boullis wrote: > On Sun, Mar 11, 2012 at 11:09:35PM -0400, Rocky Bernstein wrote: > > A patch was recently submitted: https://savannah.gnu.org/bugs/?35745 > > > > Any comments on this? > > I had no idea that identifiers t

Re: [Libcdio-devel] RFC: Savannah issue bug #35745

On Mon, Mar 12, 2012 at 8:00 AM, Robert William Fuller < hydrologiccy...@gmail.com> wrote: > On 03/12/2012 05:09 AM, Nicolas Boullis wrote: > > On Sun, Mar 11, 2012 at 11:09:35PM -0400, Rocky Bernstein wrote: > >> A patch was recently submitted: https://savannah.gnu.org/b

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Mon, Mar 12, 2012 at 8:14 AM, Pete Batard wrote: > On 2012.03.12 02:08, Rocky Bernstein wrote: > >> A lot of the concerns you have seem to be for people writing applications >> (as opposed to end users). >> > > Indeed. This is because those are compilation conce

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

uration is reliable enough to correct the mistake that we make by checking verison.h into git. On Wed, Mar 14, 2012 at 9:19 AM, Pete Batard wrote: > On 2012.03.14 10:30, Rocky Bernstein wrote: > >> So as things stand, it's fine to >> go for this provided we encapsulate

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

On Thu, Mar 15, 2012 at 11:40 AM, Pete Batard wrote: > ... > Then you are probably going to alienate MSVC users. Is the glass half empty or half full? Right now we don't *have* any MSVC users, except yourself. The steps you have taken so far then have made things easier for MSVC users for the n

[Libcdio-devel] RFC: Support for non-POSIX systems?

There has been a lot (possibly too much) back and forth regarding support for development on native Microsoft C compilers. In the past, there has been interest in supporting development on Sun's native C compiler. I realize the crowd here isn't likely to be avid Microsoft C developers, but if you

Re: [Libcdio-devel] RFC: Savannah issue bug #35745

un, Mar 11, 2012 at 11:09:35PM -0400, Rocky Bernstein wrote: > >> A patch was recently submitted: https://savannah.gnu.org/bugs/?35745 > >> > >> Any comments on this? > > > > I had no idea that identifiers that begin with _[_A-Z] were reserved, > > bu

Re: [Libcdio-devel] CD-Text API changes

On Mon, Mar 12, 2012 at 1:17 PM, Rocky Bernstein wrote: > > > On Mon, Mar 12, 2012 at 12:48 PM, leon wrote: > >> On 2012-03-12 12:12, Nicolas Boullis wrote: >> >> First I thought it to be easier this way. But the more I think about >>>> it, keeping loc

Re: [Libcdio-devel] Pete Batard's Changes (MinGW, MSVC, UDF, Joliet, header ...) merged in. Leon's CD-Text changes coming

hen when need be. There will be a version number change probably to 0.90 before release, but that's about it. So folks don't get confused, I'll also remove the MSVC project files in the master branch and make note to look in some other branch for the MSVC project files. On Mon, Mar

Re: [Libcdio-devel] RFC: Support for non-POSIX systems?

n advance of a release specifically for people who didn't want to deal with the additional requirements in building from version control. > Let me conclude. > Yes for MSVC support (and other systems if there are people caring) > No for requiring MSVC compatibility in git but providin

Re: [Libcdio-devel] RFC: Support for non-POSIX systems?

the git version lacks some files MSVC needs, there should at least be a > guide for MSVC developers of how to generate them. > > Let me conclude. > Yes for MSVC support (and other systems if there are people caring) > No for requiring MSVC compatibility in git but providing a guide &

Re: [Libcdio-devel] RFC: Support for non-POSIX systems?

do it short of something like treating these as two possibly strongly aligned or related projects. On Wed, Mar 21, 2012 at 10:24 PM, Pete Batard wrote: > On 2012.03.21 10:02, Rocky Bernstein wrote: > >> I am a convinced Linux user but imho as long as the projects using libcdio >

[Libcdio-devel] OSX 10.6 patch testing?

In short, a patch was applied to libcdio, but I don't have a means to test it. I'd appreciate it if those of you who do have OSX could try building from libcdio from git to see make sure things aren't broken. An issue was reporited in https://savannah.gnu.org/bugs/?30019 where libcdio doesn't buil

[Libcdio-devel] Planning releases of libcdio language bindings

greenleon has graciously updated all of the libcdio language bindings (Perl, Python, Ruby) for the new CD-Text API while still tolerating the old API for older libcdio versions. I am still slowly making my way through the updates. The plan is to release the language bindings in advance of the next

Re: [Libcdio-devel] W32 problems

I spent some time today looking at these patches. While there are probably some aspects that will help things, it doesn't look like I can apply any of these as is. In some cases things might be worse in other environments. Are these patches go again the current git sources. If not please use git s

Re: [Libcdio-devel] W32 problems

You have a CC this time, but I think this will be the last time from me. If you post to a developers mailing list, especially one of as low volume of this then you should be prepared to read it. If you want personal email you should use the bug tracker. In fact, that is where bugs generally are re

[Libcdio-devel] Reducing bloated test output

When you run 'make test" there is lots and lots of extraneous output. So with commit 74b0b02 I have added Makefile target "check-short". It runs make and filters out extraneous output, although it requires Ruby to help with the filtering. (t could be with POSIX shell and grep or of the other progr

[Libcdio-devel] Release 0.90 around Oct 27

It's that time of year again. I'm planning a release around Oct 27th so now is the time to test or give comments. Thanks.

Re: [Libcdio-devel] Release 0.90 around Oct 27

around you can always set the loglevel things that are errors or above. But right now I am at a loss as to why what looks like filesystems under / are being queried. On Wed, Oct 10, 2012 at 5:10 AM, Adrian Reber wrote: > On Tue, Oct 09, 2012 at 10:50:37PM -0400, Rocky Bernstein wrote: > >

Re: [Libcdio-devel] Release 0.90 around Oct 27

You are in luck. Without too much trouble I was able to reproduce this. Git commit b62ea79 I think should address this. On Wed, Oct 10, 2012 at 5:10 AM, Adrian Reber wrote: > On Tue, Oct 09, 2012 at 10:50:37PM -0400, Rocky Bernstein wrote: > > It's that time of year again.

Re: [Libcdio-devel] autoheader in the global namespace

All #define's in cdio_config.h should start CDIO_. For example: #define CDIO_PACKAGE "libcdio" The transformation is done inside include/cdio/Makefile.am. For GNU/Linux, the relevant portion expands in Makefile to: @/bin/sed -r -e 's/^(#[ \t]*define) /\1 CDIO_/' $(top_builddir)/config.h >

Re: [Libcdio-devel] autoheader in the global namespace

*/ >> #define PACKAGE_TARNAME "libcdio" >> >> /* Define to the home page for this package. */ >> #define PACKAGE_URL "" >> >> /* Define to the version of this package. */ >> #define PACKAGE_VERSION "0.83" >> >> Rob

[Libcdio-devel] Fwd: autoheader in the global namespace

in advance of last year's release, maybe we wouldn't have made the mistakes made last year. -- Forwarded message -- From: Rocky Bernstein Date: Thu, Oct 11, 2012 at 11:14 PM Subject: Re: [Libcdio-devel] autoheader in the global namespace To: libcdio developer's mai

Re: [Libcdio-devel] Fwd: autoheader in the global namespace

things work and the ins/outs. I suppose I will find out soon enough > as I try to package my own application for Debian. > > Rob > > > On 10/12/2012 04:48 AM, Rocky Bernstein wrote: > >> Folks - >> >> I had been debating to let this drop with that comment I origin

Re: [Libcdio-devel] autoheader in the global namespace

0.83. It's a shame that autotools won't put a >> prefix on there for you. I think this would be better (allow for more >> whitespace variation:) >> >> @/bin/sed -r -e 's/^([ \t]*#[ \t]*define[ \t]*)/\1CDIO_/' >> $(top_builddir)/config.h>>**

Re: [Libcdio-devel] cd-text not working for bin/cue driver?

On Wed, Oct 17, 2012 at 7:16 PM, Robert William Fuller < hydrologiccy...@gmail.com> wrote: > Also, there does not seem to be a unit test for getting cd-text from > bin/cue which is perhaps why this was missed? > > There IS a unit test for getting cd-text from nrg (Nero) files. I guess what you a

Re: [Libcdio-devel] cd-text not working for bin/cue driver?

It would help to have a some complete small standalone code (akin to the code in examples) that we could use in a test rather than a function extracted from some larger piece of code. Thanks. On Wed, Oct 17, 2012 at 6:53 PM, Robert William Fuller < hydrologiccy...@gmail.com> wrote: > As promise

Re: [Libcdio-devel] cd-text not working for bin/cue driver?

Simplest here (and I like simple here) is to use "git push" where origin/master are set to the savanah git repository. But in that push, please also add a test. Thanks. If you want to have lots of commits privately for your own purposes that's okay too. But again, before pushing to master please

Re: [Libcdio-devel] [PATCH 1/4] Add read_iso_file helper function in iso-read

Christophe - Thanks for the enhancements and patches. I tried applying the first patch to current git sources (ff3eb9f22d6138fc85695f55ff66ec2e4c3837dc) r and I get: patching file src/iso-read.c Hunk #1 FAILED at 200. Hunk #2 FAILED at 274. 2 out of 2 hunks FAILED -- saving rejects to f

Re: [Libcdio-devel] [PATCH 1/4] Add read_iso_file helper function in iso-read

The first two patches are now in git. The next two cause tests to start failing so that hasn't been applied yet. On Fri, Oct 19, 2012 at 5:57 AM, Christophe Fergeau wrote: > Hi, > > On Thu, Oct 18, 2012 at 08:03:06PM -0400, Rocky Bernstein wrote: > > I tried applying the fi

Re: [Libcdio-devel] candidate tarballs for testing.

te packages that you have to download and build prior to > building libcdio? Or can all of the dependencies be installed from > the Cygwin installer? For example, there does not seem to be a > libcddb package for Cygwin. > > On Sun, Oct 21, 2012 at 8:42 PM, Rocky Bernstein > w

Re: [Libcdio-devel] Isofs-m1 test failing

Yes please update git. Thanks. On Wed, Oct 24, 2012 at 1:26 PM, Leon Merten Lohse wrote: > 2nd try.. for some reason all gpg signed e-mails to this list are > getting blocked. > > Hi, > > while cleaning up check_cue.sh I noticed `cd-info no Rock-Ridge CUE test > ISO 9660 mode1 CUE' to be failing.

Re: [Libcdio-devel] problems with sed test

I think you are correct, and this is now in git commit 8992c19 with one addition: set SED if it is not previously set. In other words, this line: test -n "$SED" || SED=$ac_path_SED On Fri, Oct 26, 2012 at 12:34 PM, Robert William Fuller < hydrologiccy...@gmail.com> wrote: > Consider the fol

[Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

On ftp.gnu.org are releases libcdio 0.90 and libcdio-paranoia10.2+0.90. Many thanks to all that have contributed to this release including (but not limited to): Leon Merten Lohse, Pete Batard, Thomas Schmitt, LRN, Robert William Fuller, Natalia Portillo, and Christophe Fergeau. It is to you all th

Re: [Libcdio-devel] git repository for libcdio-paranoia

https://github.com/rocky/libcdio-paranoia (This was before you mentioned about http://gitorious.org) On Sun, Oct 28, 2012 at 11:01 AM, Robert William Fuller < hydrologiccy...@gmail.com> wrote: > Where is the git repository for libcdio-paranoia? > > Thank you. > > Rob > > >

Re: [Libcdio-devel] git repository for libcdio-paranoia

; with the following line in paranoia.h: > > #include > > This resulted in the following error when trying to include paranoia.h: > > /usr/local/include/cdio/**paranoia.h:18:32: fatal error: > cdio/paranoia/cdda.h: No such file or directory > > Rob > > > O

Re: [Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

4c30a84 should address all of these. On Mon, Oct 29, 2012 at 6:48 AM, Adrian Reber wrote: > On Sat, Oct 27, 2012 at 07:21:29PM -0400, Rocky Bernstein wrote: > > On ftp.gnu.org are releases libcdio 0.90 and libcdio-paranoia10.2+0.90. > > Thanks for the release. Three smaller p

Re: [Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

Should be the same as cdparanoia. Do me a favor, submit a patch to address all of the things you find. Thanks. On Fri, Nov 2, 2012 at 9:14 AM, Adrian Reber wrote: > On Mon, Oct 29, 2012 at 11:48:13AM +0100, Adrian Reber wrote: > > On Sat, Oct 27, 2012 at 07:21:29PM -0400, Rocky Bernst

Re: [Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

Applied now. Please double check. On Sun, Nov 4, 2012 at 2:36 PM, Adrian Reber wrote: > On Fri, Nov 02, 2012 at 10:21:34AM -0400, Rocky Bernstein wrote: > > Should be the same as cdparanoia. Do me a favor, submit a patch to > address > > all of the things you find. Thanks. >

Re: [Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

changes the license headers of > lib/paranoia to LGPv2+ instead of GPLv2+. Sorry, you need to revert my > previous patch. > > Adrian > > On Sun, Nov 04, 2012 at 02:53:30PM -0500, Rocky Bernstein wrote: > > Applied now. Please double check. > > > &

Re: [Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

Applied again. Please double check again. Thanks. On Sun, Nov 4, 2012 at 4:59 PM, Adrian Reber wrote: > True, attached is a new patch on top of the previous. > > > On Sun, Nov 04, 2012 at 04:45:46PM -0500, Rocky Bernstein wrote: > > Going back on a public repository is prob

Re: [Libcdio-devel] lsn versus lba versus msf

libcdio was developed far before libcddb so it probably got the mistake from libcdio. For libcdio's confusion, you probably have to go back to vcdimager. But my recollection was that LBA referred to one of two things, I think FreeBSD was different than other places, but I'm not sure and would have

Re: [Libcdio-devel] lsn versus lba versus msf

Thanks for the information. The text in the section that Thomas refers to now reads: When programming, unless one is working with a CD-DA (and even here, only > in a time-like fashion), is generally more cumbersome to use an MSF rather > than a LBA or LSN described below, since subtraction of two

Re: [Libcdio-devel] libcdio 0.90 and libcdio-paranoia 10.2+0.90 released

Reber wrote: > On Sat, Oct 27, 2012 at 07:21:29PM -0400, Rocky Bernstein wrote: > > On ftp.gnu.org are releases libcdio 0.90 and libcdio-paranoia10.2+0.90. > > Another question concerning libcdio-paranoia and its include files. > Using git commit b2807f3c7a > "Makefile.am: i

Re: [Libcdio-devel] Fix crash when trying to copy UDF root files with iso-read

Patched pulled from repository and is in git.sv.gnu.org's git now. Thanks! On Thu, Nov 22, 2012 at 8:18 AM, Christophe Fergeau wrote: > Hey, > > While experimenting with iso-read UDF support, I tried to copy > all the files from an UDF image, and I got reliable crashes > when trying to copy file

Re: [Libcdio-devel] pycdio

On Mon, Jan 7, 2013 at 4:09 PM, Adrian Reber wrote: > Is pycdio still maintained? It fails to build with the latest libcdio > release? > I don't think you were using current git sources. I've just put out release 0.18 which has some slight changes over what was in git since last April. > > swi

Re: [Libcdio-devel] W32 problems

On Sun, Jan 20, 2013 at 11:52 AM, LRN wrote: > -BEGIN PGP SIGNED MESSAGE- > > Tried 0.90 release. > Compiles out of the box ok. > Testuite runs OK OOTSD, all tests pass, except for testisocd. > 3 tests were skipped: > > testgetdevices test skipped until drive recording testing issues reso

Re: [Libcdio-devel] pycdio 0.18 missing symbols

Sorry about that. MIN_DRIVER was deprecated a while ago. ChangeLogs show circa 2009-07-12. It just takes a while for the binding libraries to catch up. If you've been following the low-volume email on libcdio-devel, this is a somewhat major incompatibility release. And that was discussed probabl

Re: [Libcdio-devel] pycdio 0.18 missing symbols

On Sun, Jan 27, 2013 at 7:34 PM, Thomas Vander Stichele < tho...@apestaart.org> wrote: > Huh. On Fedora Rawhide (which carries pycdio 0.18) things are even > worse than I expected: > > [thomas@otto ~]$ mach -r fde64 chroot > Entering /var/lib/mach/roots/fedora-development-x86_64-core, type exit >

Re: [Libcdio-devel] pycdio 0.18 missing symbols

On Sun, Jan 27, 2013 at 8:36 PM, Thomas Vander Stichele < tho...@apestaart.org> wrote: > Hi Rocky, > > > > File "/usr/lib64/python2.7/site-packages/pycdio.py", line 411, in > > > > > > CDTEXT_ARRANGER = _pycdio.CDTEXT_ARRANGER > > > AttributeError: 'module' object has no attribute 'CDTEXT_A

Re: [Libcdio-devel] pycdio 0.18 missing symbols

On Mon, Jan 28, 2013 at 2:46 PM, Thomas Vander Stichele < tho...@apestaart.org> wrote: > > > > > File "/usr/lib64/python2.7/site-packages/pycdio.py", line 411, in > > > > > > > > > > CDTEXT_ARRANGER = _pycdio.CDTEXT_ARRANGER > > > > > AttributeError: 'module' object has no attribute 'CDTEXT

[Libcdio-devel] new pycdio version of pycdio (0.19)

This release which is now on ftp.gnu.organd pypi.org is mostly a bug-fix release in order to deal with libcdio <= 0.83 versus >= 0.90 CD-Text code. Specifically, we need to be more aggressive about removing

Re: [Libcdio-devel] Work around "lt-" prefix bug in help2man

I think the patch should go in exactly in as is. (Best as I can tell from the Changelog, the --libtool option was available a year before that patch was added. I added that 2012-02-19) There are 3 ways this could be added in the order of my preference: 1. I can add you as a project member to lib

Re: [Libcdio-devel] Revisit cdio_config.h do we need this?

There are various optional features like Rock-Ridge support is available, whether libcddb was expected that are useful to know at run time. Even without this, if you want to write a simple C program like one in the examples program, one can use cdio_config.h to get a reasonable set of C defines wi

  1   2   3   4   5   6   >