Debian license file

It will update the date automatically. Here is a sample changelog file for hello:. Notice that the version has a -0ubuntu1 appended to it, this is the distro revision, used so that the packaging can be updated to fix bugs for example with new uploads within the same source release version.

Ubuntu and Debian have slightly different package versioning schemes to avoid conflicting packages with the same source version. If a Debian package has been changed in Ubuntu, it has ubuntuX where X is the Ubuntu revision number appended to the end of the Debian version. So if the Debian hello 2. If a package for the application does not exist in Debian, then the Debian revision is 0 e. For further information, see the changelog section Section 4.

The control file contains the information that the package manager such as apt-get , synaptic , and adept uses, build-time dependencies, maintainer information, and much more. For the Ubuntu hello package, the control file looks something like this:. The first paragraph describes the source package including the list of packages required to build the package from source in the Build-Depends field.

Note that in Ubuntu, we set the Maintainer field to a general address because anyone can change any package this differs from Debian where changing packages is usually restricted to an individual or a team. This can be done automatically with the update-maintainer script available in the ubuntu-dev-tools package.

For further information, see the Debian Maintainer Field spec on the Ubuntu wiki. For further information, see the control file section Chapter 5 of the Debian Policy Manual. This file gives the copyright information for both the upstream source and the packaging. Ubuntu and Debian Policy Section This file should include such information as the names of the author and the packager, the URL from which the source came, a Copyright line with the year and copyright holder, and the text of the copyright itself.

An example template would be:. You are encouraged to use this format as well. The last file we need to look at is rules. This does all the work for creating our package. It is a Makefile with targets to compile and install the application, then create the. It also has a target to clean up all the build files so you end up with just a source package again. Let us go through this file in some detail. In order to see what commands are run in each target, run:. There's no simple command that I know of.

You can do something like this: dpkg-deb --fsys-tarfile foo. Improve this answer. Josh Lee Josh Lee k 36 36 gold badges silver badges bronze badges. Specially if I want to do this for hundreds of packages. I guess a foolproof solution does not exist then. Update Many packages still have not transitioned to machine-readable license files. The only online service to check for license metadata is the "Copyright File" link on the package page on packages.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library or with a work based on the Library on a volume of a storage or distribution medium does not bring the other work under the scope of this License. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License.

If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish. Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

You may copy and distribute the Library or a portion or derivative of it, under Section 2 in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library".

Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library because it contains portions of the Library , rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not.

Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions ten lines or less in length , then the use of the object file is unrestricted, regardless of whether it is legally a derivative work.

Executables containing this object code plus portions of the Library will still fall under Section 6. Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License.

You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions. A suitable mechanism is one that 1 uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and 2 will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed in either source or binary form with the major components compiler, kernel, and so on of the operating system on which the executable runs, unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.