| Message ID | 1357757772-10661-2-git-send-email-c.schoenert@gmail.com |
|---|---|
| State | Superseded |
| Headers | show |
Dear Carsten Schoenert, On Wed, 9 Jan 2013 19:56:12 +0100, Carsten Schoenert wrote: > + DVB analyzer / MPEG analyzer program to monitor, analyze, debug, > + dump or view dvb/mpeg/dsm-cc/mhp stream information (TS, PES, > + SECTION) (e.g. digital television) send via satellite, cable or > + terrestrial. Could you include a bit more details here? You have a lot of nice details in your commit log, what about copy/pasting them here? > +DVBSNOOP_LICENSE_FILE = COPYING Should be _LICENSE_FILES even if there is only one file. Thanks, Thomas
Hello Thomas, Am 09.01.2013 21:07, schrieb Thomas Petazzoni: >> + DVB analyzer / MPEG analyzer program to monitor, analyze, debug, >> + dump or view dvb/mpeg/dsm-cc/mhp stream information (TS, PES, >> + SECTION) (e.g. digital television) send via satellite, cable or >> + terrestrial. > > Could you include a bit more details here? You have a lot of nice > details in your commit log, what about copy/pasting them here? I don't know what you exactly mean. Do you want more details in the commit message or more explanation here on the mailing list? I thought while everybody can read the commit message I don't have to explain it twice. :-/ And the webpage of dvbsnoop is written very well and the author can explain it's work better than me (I think). So what is dvbsnoop? Dvbsnoop is just a simple tool to analyze, view or debug a transport stream (TS), program elementary stream (PES) or even a program stream (PS). This input comes mostly direct from a frontend (satellite or cable tuner inside a set-top box for example) via DVB APIv3 to view into a TS, a demux to view PES or PS (also mostly inside the set-top box or even PCI Card) or even from a file (recorded TS). The device files are differ from hardware to hardware this can be given as parameter to dvbsnoop. Dvbsnoop itself doesn’t do the tuning on the frontend, this has to be done by external helpers or manually driver call. It just takes the data from it an do the parsing. The dvbsnoop tool was written while developing the software Neutrino on the set-top box DBox2 [1]. It was useful to see if the GUI Neutrino was working correct with the digital data from the frontend or from a NFS Share. In the last time Rainer Scherg doesn't has worked on dvbsnoop because it's doing what it should. Some parts are re workable, the complete latest standards for integrating the MPEG4 standards (DVB-[S,C,T]*2*) are just "it works". Some flags for this dvbsnoop don’t know right now. > Should be _LICENSE_FILES even if there is only one file. O.K. Will rework this. [1] http://en.wikipedia.org/wiki/DBox2 Regards Carsten
Dear Carsten Schoenert, On Thu, 10 Jan 2013 20:27:03 +0100, Carsten Schoenert wrote: > I don't know what you exactly mean. Do you want more details in the > commit message or more explanation here on the mailing list? Sorry, I explained improperly my request. Your commit log is absolutely perfect and gives a very nice description of what dvbsnoop is. The only minor comment I had is that the help text of your BR2_PACKAGE_DVBSNOOP option (which corresponds to the package you're adding) doesn't have as many details as your commit log as. So I was simply suggesting to copy/paste a few more details from your commit log into the help text of the BR2_PACKAGE_DVBSNOOP option. That's all! > I thought while everybody can read the commit message I don't have to > explain it twice. :-/ Sure, sure. See my explanation above. I was probably unclear in my previous e-mail. Thanks a lot for your contribution, and sorry for my previous unclear e-mail. Best regards, Thomas
Hello Thomas, Am 10.01.2013 20:45, schrieb Thomas Petazzoni: > Sure, sure. See my explanation above. I was probably unclear in my > previous e-mail. > > Thanks a lot for your contribution, and sorry for my previous unclear > e-mail. No problem at all. I understand what you want to say and I also like to see not just "BR_PACKAGE_BLUE --> It lights blue" (in backing to a famous scene in one of the Rambo films :P ). I will grabbing your suggestions and add a more precise help text later. Unfortunately many other target needs this rework also. :-) Regards Carsten
diff --git a/package/Config.in b/package/Config.in index bd1db6b..84a53a2 100644 --- a/package/Config.in +++ b/package/Config.in @@ -218,6 +218,7 @@ endif source "package/dmidecode/Config.in" source "package/dmraid/Config.in" source "package/dvb-apps/Config.in" +source "package/dvbsnoop/Config.in" source "package/eeprog/Config.in" source "package/evtest/Config.in" source "package/flashrom/Config.in" diff --git a/package/dvbsnoop/Config.in b/package/dvbsnoop/Config.in new file mode 100644 index 0000000..afd0bc5 --- /dev/null +++ b/package/dvbsnoop/Config.in @@ -0,0 +1,9 @@ +config BR2_PACKAGE_DVBSNOOP + bool "dvbsnoop" + help + DVB analyzer / MPEG analyzer program to monitor, analyze, debug, + dump or view dvb/mpeg/dsm-cc/mhp stream information (TS, PES, + SECTION) (e.g. digital television) send via satellite, cable or + terrestrial. + + http://dvbsnoop.sourceforge.net/ diff --git a/package/dvbsnoop/dvbsnoop.mk b/package/dvbsnoop/dvbsnoop.mk new file mode 100644 index 0000000..e987dc6 --- /dev/null +++ b/package/dvbsnoop/dvbsnoop.mk @@ -0,0 +1,12 @@ +############################################################# +# +# dvbsnoop +# +############################################################# + +DVBSNOOP_VERSION = 1.4.50 +DVBSNOOP_SITE = http://downloads.sourceforge.net/project/dvbsnoop/dvbsnoop/dvbsnoop-$(DVBSNOOP_VERSION) +DVBSNOOP_LICENSE = GPLv2 +DVBSNOOP_LICENSE_FILE = COPYING + +$(eval $(autotools-package))