Best practices for Source control Post: 302364568

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Scripting Best Practices

Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts. All I know so far is that I should avoid putting...

2. UNIX for Advanced & Expert Users

emergency shutdown best practices.

Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server? I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not...

3. Solaris

Best practices

Dear all, Kinda lame question but i'd like to hear your experiences and advice. Question in short ----------------- What permission should a mount point "ideally" have - i think it's root. Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another...

4. Linux

Virtualization best practices

Hello admins and gurus I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -...

LEARN ABOUT HPUX

dcontrol

DCONTROL(1)															       DCONTROL(1)

NAME

       dcontrol -- Query package and source control files for all Debian distributions

SYNOPSIS

       dcontrol [options] package[modifiers] [...]

DESCRIPTION

       dcontrol queries a remote database of Debian binary and source package control files. It can be thought of as an apt-cache webservice that
       also operates for distributions and architectures different from the local machine.

MODIFIERS

       Like apt-cache, packages can be suffixed by modifiers:

       =version
	   Exact version match

       @architecture
	   Query this only architecture. Use @source for source packages, @binary excludes source packages.

       /[archive:][suite][/component]
	   Restrict to archive (debian, debian-backports, debian-security, debian-volatile), suite (always codenames, with the exception of
	   experimental), and/or component (main, updates/main, ...). Use two slashes (//) to separate suite and component if the suite name
	   contains slashes.  (Component can be left empty.)

       By default, all versions, suites, and architectures are queried. Refer to http://qa.debian.org/cgi-bin/dcontrol for currently supported
       values.

OPTIONS

       -s, --show-suites
	   Add headers showing which distribution the control file is from.

       -d, --debug
	   Print URL queried.

       -h, --help
	   Show a help message.

       -V, --version
	   Show version information.

CONFIGURATION VARIABLES

       The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables.
       Command line options can be used to override configuration file settings.  Environment variable settings are ignored for this purpose.  The
       currently recognised variable is:

       DCONTROL_URL
	   URL to query. Default is http://qa.debian.org/cgi-bin/dcontrol.

AUTHOR

       This program is Copyright (C) 2009 by Christoph Berg <myon@debian.org>.

       This program is licensed under the terms of the GPL, either version 2 of the License, or (at your option) any later version.

SEE ALSO

       apt-cache(1).

Debian Utilities						    2013-12-23							       DCONTROL(1)