[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: dhcp-probe, another try to request with a lot of update

On Thu, Nov 27, 2008 at 10:14:56PM +0100, Laurent Guignard wrote:
> Michal ??iha?? a écrit :
> > Hi
> > 
> > [...]
> > 
> > Quick look at the package:
> > 
> > - any reason why it is Architecture: i386?
> In reason of the libraries dependency.
> libnet1 package is for i386 architecture and dhcp_probe use it with
> previous update of this library in order to provide specific functions
> needed by dhcp_probe.
> #apt-cache show libnet1
> 	Package: libnet1
> 	*Architecture: i386*

That shows the binary package information on your system.  If you'd run that
on an arm system, dhcp-probe would now be an arm-only package.

Examine the source package info, or just look at
http://packages.debian.org/sid/libnet1 for the list of architectures that a
package is built for.

But at any rate, your argument is bollocks -- packages should have the
architectures listed that *it* supports, regardless of it's dependencies. 
What if libnet1 *was* an i386-only package at the moment, but then in a
month's time someone makes it truly arch-neutral and it builds for all
arches?  Much easier for everyone if your package doesn't need any changes
to support more arches.

> May be i am wrong, but i think it is impossible to build a package on
> architectures that are not supported by needed libraries ?

It's impossible to build, yes, but that situation will be adequately dealt
with by the autobuilders.

> > - why you manually create some directories and files? dh_install and
> > dh_installdirs should do the job better and nicer. Anyway most of these
> > dirs do not have to be created (examples) or look simply wrong to me
> > (/etc/default/dhcp-probe)


> The /etc/default/dhcp-probe directory is used to store all configuration
> files needed (one for each interface on which dhcp-probe is used). I
> thought that it was the best solution instead of spreading all
> configuration files directly in /etc.

dh_installinit will automatically put a default file in place if
asked nicely.  See the appropriate man page for more details.

- Matt

Reply to: