Re: About control files
Hi, DEBIAN/control is automatically generated during package building and is used by the resulting .deb debian/control is the one you write yourself, with Descriptions and Build-Depends and stuff. Hope this clarifies things for you :) Lawrence Lucas Di Pentima wrote: Hello! I'm reading the Policy Manual so I can correct any errors I have in my control file before sending my program to Lucas Wall, that had accepted to be my sponsor. Reading this URL: http://www.debian.org/doc/debian-policy/ch-controlfields.html ...I see that the source package control file must be in debian/control, and the binary control file must be in DEBIAN/control...am I right? they are different directories? I didn't knew that. Regards, -- Lucas Di Pentima - Santa Fe, Argentina - Jabber ID: [EMAIL PROTECTED] LUNIX S.R.L. - Soluciones en GNU/Linux - http://www.lunix.com.ar GnuPG Public Key: http://random.sks.keyserver.penguin.de:11371/pks/lookup?op=getsearch=0x6AA54FC9 Key fingerprint = BD3B 08C4 661A 8C3B 1855 740C 8F98 3FCF 6AA5 4FC9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: About control files
On 03/17/2005 12:59 PM, Lucas Di Pentima wrote: Hello! I'm reading the Policy Manual so I can correct any errors I have in my control file before sending my program to Lucas Wall, that had accepted to be my sponsor. Reading this URL: http://www.debian.org/doc/debian-policy/ch-controlfields.html ...I see that the source package control file must be in debian/control, and the binary control file must be in DEBIAN/control...am I right? they are different directories? I didn't knew that. The binary control file is built from your source control file when you compile your source package into a binary package. Check the directory srctopdir/debian/pkgname/DEBIAN (pkgname may be tmp, or something else, if you are building a multi-binary package) after you build your package (and before you do a clean). Or extract the control.tar.gz file from the deb file using ar[1]. K. [1] man deb -- Lucas Wall [EMAIL PROTECTED] .''`. Buenos Aires, Argentina: :ø : Debian GNU/Linux http://www.kadath.com.ar `. `' http://www.debian.org PGP: 1024D/84FB46D6 `- 5D25 528A 83AB 489B 356Ahttp://people.debian.org/~lwall 4087 BC9B 4733 84FB 46D6mailto:[EMAIL PROTECTED] signature.asc Description: OpenPGP digital signature
Re: About control files
On Thu, Mar 17, 2005 at 12:59:40PM -0300, Lucas Di Pentima wrote: Hello! I'm reading the Policy Manual so I can correct any errors I have in my control file before sending my program to Lucas Wall, that had accepted to be my sponsor. Reading this URL: http://www.debian.org/doc/debian-policy/ch-controlfields.html ...I see that the source package control file must be in debian/control, and the binary control file must be in DEBIAN/control...am I right? they are different directories? I didn't knew that. Right. The source control file ./debian/control is the one that you modify. ./DEBIAN/control is created by dpkg-gencontrol *from* the data in the source control file. One change that you will notice is if the source control has Architecture: any (this package may be built for any architecture). In that case, the *binary* control file will have a specific Architecture: line.(i386 if built on that machine, etc.) Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: About control files
Lucas Di Pentima a écrit : I see that the source package control file must be in debian/control, and the binary control file must be in DEBIAN/control...am I right? they are different directories? I didn't knew that. that DEBIAN directory is the one generated in a binary package, where the only part in debian/control relevant to this package will be copied. Said differently, debian/control contains the source package control, then all the binary controls that will be copied in their respective temporary tree before generating the deb archive. -- Hervé Cauwelier http://www.oursours.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: About control files
also sprach Justin Pryzby [EMAIL PROTECTED] [2005.03.17.1713 +0100]: Right. The source control file ./debian/control is the one that you modify. ./DEBIAN/control is created by dpkg-gencontrol *from* the data in the source control file. ... and the changelog file. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
Re: About control files
Lucas Wall [EMAIL PROTECTED] schrieb: On 03/17/2005 12:59 PM, Lucas Di Pentima wrote: Hello! I'm reading the Policy Manual so I can correct any errors I have in my control file before sending my program to Lucas Wall, that had accepted to be my sponsor. Reading this URL: http://www.debian.org/doc/debian-policy/ch-controlfields.html ...I see that the source package control file must be in debian/control, and the binary control file must be in DEBIAN/control...am I right? they are different directories? I didn't knew that. The binary control file is built from your source control file when you compile your source package into a binary package. ... if you use dh_gencontrol(1), or invoke dpkg-gencontrol manually. Of course a package can also be created along mkdir tmp cp whatnot/ tmp/ mkdir tmp/DEBIAN cat tmp/DEBIAN/control type whatever you like Ctrl-D dpkg-deb -b tmp (you can even use tar and ar instead of dpkg-deb) Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Source code extracted to current directory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi mentors When we have a program xyz.tgz and when uncompressing it, it extracts everything to the current directory and not to xyz/ we have to create a dir xyz-version/, move all the extracted files to xyz-version/ and repack this directory, right? Thank you Nelson -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCOd+BAQwuptkwlkQRAmKwAJ4mZGty1H2Rma6/iWWFY3S7JA+IwACfdZ7c VwZqnlpkLDIGXLLzqaK9mMo= =vCfs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Source code extracted to current directory
On Thu, Mar 17, 2005 at 04:50:27PM -0300, Nelson A. de Oliveira wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi mentors When we have a program xyz.tgz and when uncompressing it, it extracts everything to the current directory and not to xyz/ we have to create a dir xyz-version/, move all the extracted files to xyz-version/ and repack this directory, right? No, dpkg-source copes with this situation fine, if it extracts in toplevel, or has a wrongly-named single directory, it'll make sure it gets in package-version/ directory anyway. Repacking should normally only be done if it contains undistributeable stuff, or non-free stuff in case of a main or contrib package. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Source code extracted to current directory
On Thu, Mar 17, 2005 at 08:54:50PM +0100, Jeroen van Wolffelaar wrote: On Thu, Mar 17, 2005 at 04:50:27PM -0300, Nelson A. de Oliveira wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi mentors When we have a program xyz.tgz and when uncompressing it, it extracts everything to the current directory and not to xyz/ we have to create a dir xyz-version/, move all the extracted files to xyz-version/ and repack this directory, right? No, dpkg-source copes with this situation fine, if it extracts in toplevel, or has a wrongly-named single directory, it'll make sure it gets in package-version/ directory anyway. Repacking should normally only be done if it contains undistributeable stuff, or non-free stuff in case of a main or contrib package. In which case you should follow the naming practice as in the Developers Reference. Note that dh_make may require that the directory be renamed, but that's a one-time thing; after that, dpkg-source will cope. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
