Sun 06 Jan 2013 03:58:31 AM UTC, comment #5:
I will add the 2 missing paragraphs to the statements. Will you need to see the modification before approving this project?
Since you seem picky about licensing statements, I have a
question about manual pages contained in separate files. Could
a statement similar to the following one, placed at the start of
a manual page (inside comments) be accepted:
// progname.1.txt - manual page documenting the program progname
// Copyright © year me
// This file is part of progname.
//
// This file is released under the same licensing terms as the source code of
// the program which it documents; see the header of the file progname.c.
|
Fri 04 Jan 2013 12:47:46 AM UTC, comment #4:
The licence header of 'nrgtool' and 'raw96cdconv' aren't complete. The statement (for the GPL) should look like this:
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
|
Wed 02 Jan 2013 09:34:42 PM UTC, comment #3:
> Wed 02 Jan 2013 12:24:27 PM CET, comment #2:
> License headers required in source code:
Could you be more specific please, because it seems that the following requirements are already fullfilled, as explained below.
> Before releasing your project under the license you choose, you
> must place copyright notices and permission to copy statements
> at the beginning of every file of source code.
I believe there are such statements in my source files, which are raw96cdconv (perl script) and nrgtool (perl script).
> In addition, if you haven't already, please copy the plain text
>version the license (usually this file is named "COPYING"). The
> GPL is available from <http://www.gnu.org/licenses/gpl.txt>.
There is a file COPYING in the tarball attached to this item, which contains the GPL v2 text.
|
Wed 02 Jan 2013 11:24:27 AM UTC, comment #2:
License headers required in source code:
Before releasing your project under the license you choose, you
must place copyright notices and permission to copy statements
at the beginning of every file of source code.
In addition, if you haven't already, please copy the plain text
version the license (usually this file is named "COPYING"). The
GPL is available from <http://www.gnu.org/licenses/gpl.txt>.
Additional instructions are available from
<http://www.gnu.org/licenses/gpl-howto.html>, that are usually
valid for libre software licenses.
The GPL FAQ explains why these procedures must be followed. To
learn why a copy of the GPL must be included with every copy of
the code, for example, go to
<http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude>
|
Tue 25 Dec 2012 08:48:15 AM UTC, comment #1:
Source code required:
Please include an (temporary) URL pointing to the source code,
or attach a tarball to this item.
We wish to review your source code, even if it is not
functional, to catch potential legal issues early.
For example, to release your program properly under the GPL you
must include a copyright notice and statement permitting copying
at the beginning of every file of source code. This is
explained in <http://www.gnu.org/licenses/gpl-howto.html>. Our
review would help catch potential omissions such as these.
|
Sat 22 Dec 2012 01:12:51 PM UTC, original submission:
A new project has been registered at Gna!
This project account will remain inactive until a site admin approves or discards the registration.
Registration Administration
While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators, effectively logged as site administrators (superuser):
Registration Details
- Name: command line tools to inspect and manipulate CD image files
- System Name: cdimgtools
- Type: Programs
- License: Other, GPL Compatible (GNU General Public License V2)
Description:
CDimgtools is a small set of command line tools to inspect and manipulate CD (and possibly DVD) images of formats uncommon on Linux/UNIX systems.
You can print information about an image file and extract its tracks to files in raw format, so that they can be used with common Linux/UNIX tools (for playing audio, reading files, burning tracks or sessions to optical media
etc.).
Commands written, so far:
raw96cdconv
This command demultiplexes stream data (audio, raw data or .iso format data) and sub-channel data from a RAW+96 image file. It operates on CD images containing stream data and sub-channel data of a given sector at contiguous positions; this kind of image file may be either directly created by a ripping program like readcd(1) or cdrdao(1), or extracted from another image file by nrgtool(1).
nrgtool
This command reads .nrg images (created by Nero), prints the metadata about the image, and extracts, for each track, the raw data to a separate file. It should work with audio discs and multi-session discs.
cssdec
This command decrypts CCS-scrambled VOB files.
dvdimgdecss
This command decrypt CSS scrambled DVD Video image files. The advantages over dvdbackup et al. is that:
(1) the image is left intact, not re-created, so that non video Bonus contents is preserved
(2) some discs using non standard menu structures to prevent copies will be readable on DVD Video players, whereas copies made by dvdbackup will not.
Other Software Required:
perl 5
libdvdcss
libdvdread
|