Are You All Getting Ready for the New Options Symbology?


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Are You All Getting Ready for the New Options Symbology?
# 1  
Old 01-01-2009
Are You All Getting Ready for the New Options Symbology?

2009-01-01T12:51:00.002-05:00


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

The disk drive for /tmp is not ready yet or not present && the disk drive for /boot is not ready yet

Hi Team when I boot the server I get this 2 errors : the disk drive for /tmp is not ready yet or not present the disk drive for /boot is not ready yet or not present and its stay like that , I m using Ubuntu 12.04 please if someone have any idea how to fix that problem . (1 Reply)
Discussion started by: SULTAN01
1 Replies

2. Ubuntu

Kernel boot options removed by fault, no boot options

Hello Everyone, First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you ! I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies

3. Filesystems, Disks and Memory

ext4 - ready for production system?

Gidday, Are you using ext4 for production system? Or is it better to opt for a more conservative strategy, like ext3 for instance? What are your experiences? Thanks in advance, Loïc. (3 Replies)
Discussion started by: Loic Domaigne
3 Replies

4. Virtualization and Cloud Computing

VirtualBox 3.1 ready for download

Downloads - VirtualBox (0 Replies)
Discussion started by: DukeNuke2
0 Replies

5. Solaris

LUN not ready

hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies

6. Shell Programming and Scripting

Script ready but might need some improvement.

Hi All, I have written a script which does some editing in the files, based on user input.This might not be the most elegant way of doing it and there would be many improvements needed. Please go through it and let me know how it could be improved. Suggestions are welcome!! Thanks!... (2 Replies)
Discussion started by: nua7
2 Replies
Login or Register to Ask a Question
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)