Jaldhar H. Vyas wrote: > On Sun, 9 Nov 1997, Igor Grobman wrote: > > > on page 2, you say: > > Line 8 describes the CPU architecture the binary package was compiled > >for. We can leave this as any as debmake will fill in the appropriate > >value. > > ^^^^^^^ > > > > Actually, it's dpkg that does it. > > > > dpkg itself or dpkg-buildpackage? I've put in dpkg-buildpackage for now.
Actually, it's dpkg-gencontrol that does it. > > > still on page 2, you say regarding Pre-depends: > > > > This is stronger than depends. dpkg and dselect will not install your > > program unless the packages it Pre-depends on > > are installed and correctly configured. Use this vry sparingly. > > > > > > You should mention that if you want to use Pre-depends, you need the > > approval > > of debian-devel. > > > > I've added "...and only after discussing it on the debian-devel mailing > list." to the end of this sentence. ok. > > > on page 3 you say: > > > > We also don't want the debug options. > > > > Actually, it is recommended to compile the binary with debugging symbols in > > the build target, and then strip it in the binary. This is to ease the > > debugging for the maintainer or whoever else is working with the source > > package. > > > > You're right. But why do we strip the binary then? I think people might > be confused if we don't give the reason. We strip the binary to save space. Debugging symbols are not needed for running of the program. -- Proudly running Debian Linux! Linux vs. Windows is a no-Win situation.... Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
