Reuters Config Files - Where do they go?

4 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

(VS 2008) New build config looking files from other folder build config

Hi Team, My new build configuration always looking for the files from the build where i copied from. please help me to resolve this. I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development I created new debug_new build configuration with additional preprocessor from the...

2. Shell Programming and Scripting

Shell script that will compare two config files and produce 2 outputs 1)actual config file 2)report

Hi I am new to shell scripting. There is a requirement to write a shell script to meet follwing needs.Prompt reply shall be highly appreciated. script that will compare two config files and produce 2 outputs - actual config file and a report indicating changes made. OS :Susi linux ver 10.3. ...

3. Shell Programming and Scripting

parsing config file to create new config files

Hi, I want to use a config file as the base file and parse over the values of country and city parameters in the config file and generate separate config files as explained below. I will be using the config file as mentioned below: (config.txt) country:a,b city:1,2 type:b1...

4. HP-UX

Config Files

Does anyone have a list of key config files and the respective paths for HP-UX? Or does anyone know where I can get a list similar to this? Thanks, TOdd

LEARN ABOUT DEBIAN

config::model::models::debian::dpkg::source

Config::Model::models::Debian::Dpkg::Source(3pm)	User Contributed Perl Documentation	  Config::Model::models::Debian::Dpkg::Source(3pm)

NAME

       Config::Model::models::Debian::Dpkg::Source - Configuration class Debian::Dpkg::Source

VERSION

       version 2.021

DESCRIPTION

       Configuration classes used by Config::Model

       Model of files found under debian/source directory.  See dpkg-source for details.

Elements
   format - source package format
       Specifies the format of the source package. A missing format implies a '1.0' source format.Mandatory. Type enum. choice: '1.0', '2.0', '3.0
       (native)', '3.0 (quilt)', '3.0 (custom)', '3.0 (git)', '3.0 (bzr)'.

       Here are some explanations on the possible values:

       '1.0'
	   A source package in this format consists either of a .orig.tar.gz associated to a .diff.gz or a single .tar.gz (in that case the
	   package is said to be native).

       '2.0'
	   was the first specification of a new-generation source package format. This format is not recommended for wide-spread usage, the format
	   "3.0 (quilt)" replaces it.

       '3.0 (bzr)'
	   This format is experimental. It generates a single tarball containing the bzr repository.

       '3.0 (custom)'
	   This format is particular. It doesn't represent a real source package format but can be used to create source packages with arbitrary
	   files.

       '3.0 (git)'
	   This format is experimental. A source package in this format consists of a single bundle of a git repository .git to hold the source of
	   a package.  There may also be a .git shallow file listing revisions for a shallow git clone.

       '3.0 (native)'
	   extension of the native package format as defined in the 1.0 format.

       '3.0 (quilt)'
	   A source package in this format contains at least an original tarball (.orig.tar.ext where ext can be gz, bz2, lzma and xz) and a
	   debian tarball (.debian.tar.ext). It can also contain additional original tarballs (.orig-component.tar.ext).

   options
       Source options as described in dpkg-sourceOptional. Type node.

SEE ALSO

       o   cme

       o   Config::Model::models::Debian::Dpkg::Source::Options

AUTHOR

       Dominique Dumont

COPYRIGHT

       2010,2011 Dominique Dumont

LICENSE

       LGPL2

perl v5.14.2							    2012-11-09			  Config::Model::models::Debian::Dpkg::Source(3pm)

Complex Event Processing RSS News