Reuters Config Files - Where do they go?


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Reuters Config Files - Where do they go?
# 1  
Old 11-14-2008
Reuters Config Files - Where do they go?

2008-11-14T13:57:00.002-05:00


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

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... (1 Reply)
Discussion started by: SA_Palani
1 Replies

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. ... (4 Replies)
Discussion started by: muraliinfy04
4 Replies

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... (1 Reply)
Discussion started by: clazzic
1 Replies

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 (0 Replies)
Discussion started by: toddjameslane
0 Replies
Login or Register to Ask a Question
Config::Model::models::Debian::Dpkg::Copyright(3pm)	User Contributed Perl Documentation    Config::Model::models::Debian::Dpkg::Copyright(3pm)

NAME
Config::Model::models::Debian::Dpkg::Copyright - Configuration class Debian::Dpkg::Copyright VERSION
version 2.021 DESCRIPTION
Configuration classes used by Config::Model Machine-readable debian/copyright. Parameters from former version of DEP-5 are flagged as deprecated. The idea is to enable migration from older specs to CANDIDATE spec. To edit a copyright file, go into your package development directory and run: config-edit -application dpkg-copyright To check you file run: config-edit -application dpkg-copyright -ui none To upgrade your file from an old spec, run: config-edit -application dpkg-copyright -ui none -save Elements Format URI of the format specification.Mandatory. Type uniline. default: 'http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/'. Upstream-Name The name upstream uses for the software.Optional. Type uniline. Note: Upstream-Name is migrated with '$name' and with $name => ""- Name"" Upstream-Contact The preferred address(es) to reach the upstream project. May be free-form text, but by convention will usually be written as a list of RFC5822 addresses or URIs.Optional. Type list of uniline. Note: Upstream-Contact values are migrated from '- Upstream-Maintainer' Source An explanation from where the upstream source came from. Typically this would be a URL, but it might be a free-form explanation. The Debian Policy, 12.5 requires this information unless there are no upstream sources, which is mainly the case for native Debian packages. If the upstream source has been modified to remove non-free parts, that should be explained in this field.Optional. Type string. Note: Source is migrated with $old || $older ; and with $older => ""- Original-Source-Location"", $old => ""- Upstream-Source"" Disclaimer This field can be used in the case of non-free and contrib packages (see [Policy 12.5]( http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile))Optional. Type string. Comment This field can provide additional information. For example, it might quote an e-mail from upstream justifying why the license is acceptable to the main archive, or an explanation of how this version of the package has been forked from a version known to be DFSG-free, even though the current upstream version is not.Optional. Type string. Note: Comment is migrated with '$old' and with $old => ""- X-Comment"" Copyright Copyright information for the package as a whole, which may be different or simplified from a combination of all the per-file copyright information. See also Copyright below in the Files paragraph section.Optional. Type string. Files Patterns indicating files having the same license and sharing copyright holders. See "File patterns" below. Optional. Type hash of node. Global-License Optional. Type node. Format-Specification Deprecated Optional. Type uniline. Name Deprecated Optional. Type uniline. Maintainer Line(s) containing the preferred address(es) to reach current upstream maintainer(s). May be free-form text, but by convention will usually be written as a list of RFC2822 addresses or URIs.Deprecated Optional. Type list of uniline. Upstream-Maintainer Deprecated Optional. Type list of uniline. Note: Upstream-Maintainer values are migrated from '- Maintainer' Upstream-Source Deprecated Optional. Type string. Original-Source-Location Deprecated Optional. Type string. License Optional. Type hash of node. X-Comment Deprecated Optional. Type string. SEE ALSO
o cme o Config::Model::models::Debian::Dpkg::Copyright::Content o Config::Model::models::Debian::Dpkg::Copyright::GlobalLicense o Config::Model::models::Debian::Dpkg::Copyright::LicenseSpec AUTHOR
Dominique Dumont COPYRIGHT
2010,2011 Dominique Dumont LICENSE
LGPL2 perl v5.14.2 2012-11-09 Config::Model::models::Debian::Dpkg::Copyright(3pm)