Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

emvendor(1) [debian man page]

EMVENDOR(1)						User Contributed Perl Documentation					       EMVENDOR(1)

Name
       emvendor - retrieve vendor-specific package configuration strings

Synopsis
	emvendor -V|--vendor VENDOR -p|--package PACKAGE -k|--key KEY
	emvendor -?|-h|--help|--version

Commands
	-v|--vendor VENDOR:    the vendor name from dpkg-vendor
	-p|--package PACKAGE:  the package name (usually source)
	-k|--key KEY:	       arbitrary string for the key of the data

       All commands must be specified every time.

       On success, the string is printed and emvendor exits with zero.

       In the case of error, emvendor dies with an empty string on STDERR and exits with a non-zero return value.

Description
       emvendor provides a way for debian/rules to call in a string for a particular package that fits into the rules for that package and
       conforms to the requirements of the vendor.

       http://wiki.debian.org/EmdebianAuditDetail#Vendor

       It is fairly obvious that specifying each vendor in the debian/rules file of each package is not going to be particularly flexible.

	DEB_VENDOR=$(shell dpkg-vendor --query vendor)
	ifeq (Debian,$(DEB_VENDOR))
	 # Debian build
	 EXCONFARGS=--disable-mono --disable-monodoc
	else
	 # any-vendor build
	 EXCONFARGS=$(shell emvendor --vendor $(DEB_VENDOR) --package avahi --key EXCONFARGS)
	endif

       or use the short options:

	EXCONFARGS=$(shell foo-bar -V $(DEB_VENDOR) -p avahi -k EXCONFARGS)

       The values themselves are in a vendor-specific conf file in /etc/emvendor.d/

	$ cat /etc/foo-bar.d/emdebian-crush
	[avahi]
	EXCONFARGS=--disable-mono --disable-monodoc --disable-python
	--disable-doxygen-doc --disable-pygtk --disable-python-dbus
	--disable-core-docs --disable-qt3 --disable-qt4 --disable-gobject
	--with-distro debian

	[busybox]
	foo=

       (Note that the value has to be all on one line which is a little awkward - also note that values are not able to include the equals sign
       which could be more of an issue.)

       Packages that need two strings can do so - the key string is entirely arbitrary as long as it fits in the style of a typical ini file.

       Therefore, the key can be matched to the needs of the relevant package.

       "emdebian-buildsupport" provides /etc/emvendor.d/emdebian-crush with all the content for all packages that need such details.

emvendor and dpkg-vendor
       dpkg-vendor supports vendor functionality but emvendor adds an extra hierarchy, organised by Debian source package name. It would be
       possible to include the relevant strings in /etc/dpkg/origins/vendor but each identifier string would need to be unique across all packages
       for each vendor, which is an unrealistic limitation.

perl v5.14.2							    2012-09-26							       EMVENDOR(1)

Check Out this Related Man Page

MAC-VENDOR(5)							File Formats Manual						     MAC-VENDOR(5)

NAME
mac-vendor - Ethernet vendor file for arp-scan SYNOPSIS
mac-vendor.txt DESCRIPTION
The mac-vendor.txt contains Ethernet MAC to vendor string mappings for arp-scan. It is used in addition to the IEEE OUI and IAB listings in ieee-oui.txt and ieee-iab.txt. It is for MAC-vendor mappings that are not covered by the IEEE manufacturer listings. Each line in the mac-vendor.txt file contains a MAC-vendor mapping in the form: <MAC-Prefix><TAB><Vendor> Where <MAC-Prefix> is the prefix of the MAC address in hex, and <Vendor> is the name of the vendor. The prefix can be of any length from two hex digits (one octet) to twelve hex digits (six octets, the entire Ethernet hardware address). The alphabetic hex characters [A-F] must be entered in upper case. For example: 012345 would match 01:23:45:xx:xx:xx, where xx represents any value; 0123456 would match 01:23:45:6x:xx:xx; and 01234567 would match 01:23:45:67:xx:xx. Blank lines and lines beginning with "#" are ignored. The order of entries in the file is not important. arp-scan will attempt to match larger prefixes before trying to match smaller ones, and will stop at the first match. FILES
/usr/local/share/arp-scan/mac-vendor.txt EXAMPLE
# From nmap Debian bug report #369681 dated 31 May 2006 525400 QEMU B0C420 Bochs # From RFC 2338: 00-00-5E-00-01-{VRID} 00005E0001 VRRP (last octet is VRID) # Microsoft WLBS (Windows NT Load Balancing Service) # http://www.microsoft.com/technet/prodtechnol/acs/reskit/acrkappb.mspx 02BF Microsoft WLBS (last four octets are IP address) AUTHOR
Roy Hills <Roy.Hills@nta-monitor.com> SEE ALSO
arp-scan(1) get-oui(1) get-iab(1) arp-fingerprint(1) http://www.nta-monitor.com/wiki/ The arp-scan wiki page. March 30, 2007 MAC-VENDOR(5)
Man Page