[libdvdcss-devel] Release 1.3.0 approaching

[Jean-Baptiste Kempf]

Hello,

We've been doing quite a few things lately, which is cool. A new release
named 1.3.0 will come soon, then.

Now is the time to submit your patches that must get in the release.

Best regards,

[Fabian Greffrath]

Post by Jean-Baptiste Kempf
We've been doing quite a few things lately, which is cool. A new release
named 1.3.0 will come soon, then.

How about the controversial change to save keys in binary format, is
this definite?

- Fabian

[Jean-Baptiste Kempf]

Post by Fabian Greffrath

Post by Jean-Baptiste Kempf
We've been doing quite a few things lately, which is cool. A new release
named 1.3.0 will come soon, then.

How about the controversial change to save keys in binary format, is
this definite?

I did not see a consensus on that one, so this should wait.

[Bernard Lang]

Post by Jean-Baptiste Kempf

Post by Fabian Greffrath
How about the controversial change to save keys in binary format, is
this definite?

I did not see a consensus on that one, so this should wait.

If I may comment on this as a user:

The use of readable caches in ASCII is an old UNIX principle that
often proves useful, if only as a form of easily readable
documentation about the software concerned.

Typically, I currently have a problem communicating with K3B from a
script without using the GUI and without getting into the K3B
code. The fact that K3B data is stored in a human readable ASCII file
: ~/.kde4/share/config/k3brc (like other KDE apps that are all in
~/.kde4/share/config/) is making my life a lot easier.


Another thing that I find very helpful in a similar way is the verbose
mode and the debugging mode DVDCSS_VERBOSE="2". It helps to understand
what is going on without getting into the code, or before doing it
(which does help understand a program). My worry is that "debugging
mode" is an informal status, not intended for users, and could
possibly be altered by developpers without a second thought.

Actually, I use libdvdcss from a script by launching VLC and parsing
the "debug" messages to get the information I need, such as the
location of the cache (among several other data). If it is decided by
the development team to change the location of the cache, it does not
matter to me as I get the current location directly from the libdvdcss
execution. I find this very convenient for my purpose and a lot faster
than fighting my way in the C code.

But if you were to remove some of these "libdvdcss debug:" messages,
my program would no longer work, and I would not know how to repare
the damage with reasonable effort.

Hence I would feel a lot more comfortable if these optionnal messages
were promoted to a stronger status as a feature (an optional one as it
is now) of libdvdcss rather than being merely a debugging tool.

Bernard

Post by Jean-Baptiste Kempf

Post by Fabian Greffrath

Post by Jean-Baptiste Kempf
We've been doing quite a few things lately, which is cool. A new release
named 1.3.0 will come soon, then.

How about the controversial change to save keys in binary format, is
this definite?

I did not see a consensus on that one, so this should wait.
--
Jean-Baptiste Kempf
http://www.jbkempf.com/ - [phone]
Sent from my Electronic Device
_______________________________________________
libdvdcss-devel mailing list
http://mailman.videolan.org/listinfo/libdvdcss-devel

--
Après la bulle Internet, la bulle financière ...
Et bientôt la bulle des brevets
http://www.strategie.gouv.fr/system/files/noteveille81.pdf
http://www.huffingtonpost.com/brian-kahin/the-patent-bubble_b_129232.html
la gestion des catastrophes comme principe de gouvernement

***@datcha.net ,_ /\o \o/ gsm [phone]
http://www.datcha.net/ ^^^^^^^^^^^^^^^^^ tel [phone]
Je n'exprime que mon opinion - I express only my opinion
CAGED BEHIND WINDOWS or FREE WITH LINUX

[Diego Elio Pettenò]

https://xkcd.com/1172/
Diego Elio Pettenò — Flameeyes

Post by Bernard Lang

Post by Jean-Baptiste Kempf

Post by Fabian Greffrath
How about the controversial change to save keys in binary format, is
this definite?

I did not see a consensus on that one, so this should wait.

The use of readable caches in ASCII is an old UNIX principle that
often proves useful, if only as a form of easily readable
documentation about the software concerned.
Typically, I currently have a problem communicating with K3B from a
script without using the GUI and without getting into the K3B
code. The fact that K3B data is stored in a human readable ASCII file
: ~/.kde4/share/config/k3brc (like other KDE apps that are all in
~/.kde4/share/config/) is making my life a lot easier.
Another thing that I find very helpful in a similar way is the verbose
mode and the debugging mode DVDCSS_VERBOSE="2". It helps to understand
what is going on without getting into the code, or before doing it
(which does help understand a program). My worry is that "debugging
mode" is an informal status, not intended for users, and could
possibly be altered by developpers without a second thought.
Actually, I use libdvdcss from a script by launching VLC and parsing
the "debug" messages to get the information I need, such as the
location of the cache (among several other data). If it is decided by
the development team to change the location of the cache, it does not
matter to me as I get the current location directly from the libdvdcss
execution. I find this very convenient for my purpose and a lot faster
than fighting my way in the C code.
But if you were to remove some of these "libdvdcss debug:" messages,
my program would no longer work, and I would not know how to repare
the damage with reasonable effort.
Hence I would feel a lot more comfortable if these optionnal messages
were promoted to a stronger status as a feature (an optional one as it
is now) of libdvdcss rather than being merely a debugging tool.
Bernard

Post by Jean-Baptiste Kempf

Post by Fabian Greffrath

Post by Jean-Baptiste Kempf
We've been doing quite a few things lately, which is cool. A new release
named 1.3.0 will come soon, then.

How about the controversial change to save keys in binary format, is
this definite?

I did not see a consensus on that one, so this should wait.
--
Jean-Baptiste Kempf
http://www.jbkempf.com/ - [phone]
Sent from my Electronic Device
_______________________________________________
libdvdcss-devel mailing list
http://mailman.videolan.org/listinfo/libdvdcss-devel

--
Après la bulle Internet, la bulle financière ...
Et bientôt la bulle des brevets
http://www.strategie.gouv.fr/system/files/noteveille81.pdf
http://www.huffingtonpost.com/brian-kahin/the-patent-bubble_b_129232.html
la gestion des catastrophes comme principe de gouvernement
http://www.datcha.net/ ^^^^^^^^^^^^^^^^^ tel [phone]
Je n'exprime que mon opinion - I express only my opinion
CAGED BEHIND WINDOWS or FREE WITH LINUX
_______________________________________________
libdvdcss-devel mailing list
http://mailman.videolan.org/listinfo/libdvdcss-devel

[Fabian Greffrath]

Post by Diego Elio Pettenò
https://xkcd.com/1172/

In which way does changing the keys to binary format improve the lib?