Re: [Libcdio-devel] OS/2 patches

[Rocky Bernstein]

Please set up a virtual machine or hardware for OS/2 and eCS testing so
that the developers who want to test it can.

The slightly (but not surprising) thing about libcdio in contrast to most
other packages is that the test machine does need to have a cdrom drive
attached to it preferably with some sort of media inside. Better would be
with several drives with different media, e.g. one an audio CD and another
an ISO9660 filesystem. I suppose drives on a virtual machine would work as
well.

Access to this doesn't need to be available all the time, just when it's
needed. And we can arrange accounts/access of list. Thanks.




On Sun, Jul 27, 2014 at 5:33 PM, Natalia Portillo <address@hidden>
wrote:

> Hi all,
>
> I have no deep knowledge of the OS/2 API as to be the sole maintainer of
> it but I can set up a virtual machine for testing with any OS/2 or eCS
> version and maybe even real hw.
>
> If you need to maintain the os2 code aside of the mainstream you're
> welcome to use my GitHub fork, as when I get the time the osx patches may
> require changes to the inner libcdio workings that will make merging slow
> and painful xD
>
> I'm not always on mail but any help you need from me just drop a direct
> message.
>
> Regards
>
> Sent from my iPhone
>
> > On 27/7/2014, at 16:11, Rocky Bernstein <address@hidden> wrote:
> >
> > Sorry for the delay. Things have been busy for me.
> >
> > It is interesting to hear back after the 5 or so years. About a month
> and a
> > half ago we were discussing dropping libcdio's OS/2 driver altogether.
>  See
> > http://lists.gnu.org/archive/html/libcdio-devel/2014-06/msg00004.html
> >
> > What motivated this was the desire to change the API to add
> get_track_isrc
> > and Robert Kausch mentioned he had no way to test OS/2. In that, we
> > realized that basically no one *is* actively testing OS/2.
> >
> > Aside from yourself and possibly Natalia, do you know anyone else that is
> > using this?
> >
> > Given the low activity and difficulty for finding developers and testers,
> > I'm inclined to have this maintained by you and Natalia in separately.
> She
> > already has a fork on github of libcdio-paranoia.
> >
> > If OS/2 is to survive in libcdio, someone needs to commit to handle
> > problems and API changes as such things arise. Are you willing to commit
> to
> > this?
> >
> > Lastly, on the first patch. It has to do with deciding on whether the use
> > the libcdio-supplied getopt.c,and this is based purely on OS. OS/2 is the
> > only one to not used the supplied getopt.c
> >
> > Rather than have a test by OS, I'd prefer a test to compile the supplied
> > getopt;  if that fails, then run a test to see if there is an OS getopt.
> >
> >
> >
> >> On Sat, Jul 26, 2014 at 11:50 PM, KO Myung-Hun <address@hidden>
> wrote:
> >>
> >> Ping ?
> >>
> >> KO Myung-Hun wrote:
> >>> Hi/2, long tiem no see. ^^
> >>>
> >>> I attach the patches to build libcdio and to enhance memory usage on
> >> OS/2.
> >>>
> >>> Review, please...
> >>>
> >>>
> >>>
> >>
> >> --
> >> KO Myung-Hun
> >>
> >> Using Mozilla SeaMonkey 2.7.2
> >> Under OS/2 Warp 4 for Korean with FixPak #15
> >> In VirtualBox v4.1.32 on Intel Core i7-3615QM 2.30GHz with 8GB RAM
> >>
> >> Korean OS/2 User Community : http://www.ecomstation.co.kr
> >>
> >>
> >>
>
>