On Wed, Mar 11, 2009 at 12:30 PM, Jaromír Mikeš <[email protected]> wrote: > Hello, > > I just going through "New Maintainers' Guide" and editing debian/rules file. > > In NMG is sentence: > "If your package is an `Architecture: all' one, you need to include all the > commands for building the package under the `binary-indep' rule, and leave > the `binary-arch' rule empty instead." > > It's mean something like this? > > ############ > > # Build architecture-independent files here. > binary-indep: build install > dh_testdir > dh_testroot > dh_installchangelogs > dh_installdocs > dh_installexamples > # dh_install > # dh_installmenu > # dh_installdebconf > # dh_installlogrotate > # dh_installemacsen > # dh_installpam > # dh_installmime > # dh_python > # dh_installinit > # dh_installcron > # dh_installinfo > dh_installman > dh_link > dh_strip > dh_compress > dh_fixperms > # dh_perl > # dh_makeshlibs > dh_installdeb > dh_shlibdeps > dh_gencontrol > dh_md5sums > dh_builddeb > > > # Build architecture-dependent files here. > binary-arch: build install > > binary: binary-indep binary-arch > .PHONY: build clean binary-indep binary-arch binary install configure > > ################# >
That is the correct approach, as far as I know. Be aware that you should remove the commented "dh_*" commands prior to attempting to upload the package or getting a sponsor, see the minor issues section of http://ftp-master.debian.org/REJECT-FAQ.html -- Daniel Moerner <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
