.\" /usr/share/man/man1/makelocalsite.1(.gz) .\" author Neil Franklin, last modification 2006.12.19 .\" copyright ETH Zuerich Physics Departement .\" use under either modified/non-advertising BSD or GPL license .TH MAKELOCALSITE 1 "2006.12.19" "D-PHYS Package Tools" .SH NAME makelocalsite \- manage control files for an local Debian package site .SH SYNOPSIS .B makelocalsite [\fB-b\fP \fIbaseaddress\fP] [\fB-d\fP \fIdistributiondir\fP] [\fB-vD\fP] \fIsection\fP [\fIsection\fP ...] .PP .B makelocalsite \fB-h\fP .SH DESCRIPTION makelocalsite manages an local Debian packages server. It deletes duplicate (new and older copies) of packages to prevent error messages (only the older binary .deb files, the older sources are kept as archive, as they make no error messages), makes symlinks from architecture dependant to independant directories, generates override files, and source or packages lists. .SH OPTIONS .TP .BI \-b \ baseaddr base: Package files are uploaded relative to this base directory; default: whatever is set in CONF_PKG_BASE. .TP .BI \-d \ distribution distribution: Package are uploaded relative to this distribution; default: whatever is set in CONF_DISTRIB. .TP .B \-q quiet: Don't give user an running report of what we are doing. .TP .B \-D Debug: Activate an debug option. See source for how to use this. .TP .B \-h help: Output help text, and then abort operation. .PP .I section section name: Must be an section name valid on your site, or multiple of those. Allways valid are the standard Debian sections: \fImain\fP or \fInon-free\fP or \fIcontrib\fP. To see what other sections you have on your site, list out the directory pointed to by \fBCONF_PKG_BASE\fP/dists/\fBCONF_DISTRIB\fP. You can have any sections you want, but your hosts \fI/etc/apt/sources.list\fP files must list them to use them. .SH CONFIG The config files \fI/etc/dphys-pkgtools\fP (sitewide), \fI~/.dphys-pkgtools\fP (personal) and \fI./dphys-pkgtools\fP (particular project) allow the admin and users to set up the working environment for \fBmakelocalsite\fP (and \fBmakesourcepackage\fP also). .PP These config files are sh script fragments full of assignments, which are sourced, in above row, later config files assignments overriding earlier ones. Standard sh syntax rules apply. Assignments relevant for \fBmakelocalsite\fP are: .TP .B CONF_GROUP Make all uploaded files and directories writable by any user in this group. For use so that all members of this group can work on the package site (adding or replacing packages). Defaults to nothing, as this is usable for single user and no sensible group value can be defaulted. Usually the admin will set this. .TP .B CONF_PKG_BASE Set base directory on server for all uploads to go into. Overridable with \fB-b\fP (base). This should be the base directory of the Debian-like package archive, and will usually match the DocumentRoot of your HTTP VirtualHost. Defauls also to error message generating \fI/not/configured/directory\fP. Usually the admin will set this. .TP .B CONF_DISTRIB Set which distribution directory within our package server to use. We suggest something like \fI/local\fP, analog to how Debian does it for /non-US and /updates (on Debian security). Defaults to \fIwoody/local\fP. Change woody to whatever Debian version you are using. .TP .B CONF_BINARCH Use this binary architectures directory as target for linking to binary-all. Defaults to \fBi386\fP, as most users have this architecture. You can not process multiple architectures. .SH FILES .TP .B /etc/dphys-pkgtools site admin config .TP .B ~/.dphys-pkgtools users personal config .TP .B ./dphys-pkgtools individual projects config .SH EXAMPLES All config files are the same ones as used for \fBmakesourcepackage\fP(1), so see their setup there. Ths man page assumes you have already done that. .PP Only an subset of the assignments in the config files (the \fB-u\fP (upload) stuff) are relevant to \fBmakelocalsite\fP. They are documented there, because far more users will know that command from using it. .PP One additional assignment may possibly be wanted, if you use non-x86 systems: .PP In \fI/etc/dphys-pkgtools\fP: .PP CONF_BINARCH=whatever-you-have .PP Note that \fBmakelocalsite\fP only supports maintaining links for one single architecture at present. .PP Then the sysadmin must setup an HTTP VirtualHost which will be offering your packages. Its DocumentRoot will usually be set to the directory configured in the CONF_PKG_BASE assignment (unless you are using an subdirectory of an existing webserver), so that uploading and fetching match. The CONF_PKG_BASE must be writable by the user(s) used for uploading (CONF_USER) or the group the files and directories get set to (CONF_GROUP). .PP Users can now upload packages and manage the site. This happens fully automatically when they use \fBmakesourcepackage \-u\fP, because this calls \fBmakelocalsite\fP. If you want to rebuild the site structures without uploading an new package, you can directly invoke \fBmakelocalsite\fP with: .PP \fBmakelocalsite main\fP .PP Above will rebuild all structures pertaining to "main" section packages. Only legal alternatives are \fIcontrib\fP and \fInon-free\fP, or multiple of them, unless you have site specific own categories. .PP To actually use your local package server, do not forget to add it to the \fI/etc/apt/sources.list\fP server list on all your hosts. .SH ERROR MESSAGES These are graded into categories and marked accordingly, and then sent to stderr output: .TP .B FATAL: Something happend that was not expected to be so. Looks seriously wrong. Operation will be immediately aborted. May require sysadmin to fix. Could even be sign of an bug. .TP .B ERROR: User input looks errorneous. Will try to give out help as far as applicable help is known. Check up on command line options and filenames. .TP .B WARNING: Something unusual is happening, most likely wrong, but it may be desired. So continue operation but warn user, to look if it was an desired thing. .TP .B NOTE: Something happend which is completely legal, but may be sign of trouble. Give user a note that it happened and continue. .TP .B INFO: Tell user what we are doing now. Only happens if user demanded \-v verbosity. Not unexpected and not an error, so sent to stdout, not stderr. .TP .B DEBUG: Tell user in what state we are at the moment. Only happens if user demanded \-D PRINT_STEP debug output. Not unexpected and not an error, so sent to stdout, not stderr. .SH SEE ALSO \fIdphys-pkgtools\fP(7), \fImakesourcepackage\fP(1) .SH AUTHOR franklin@phys.ethz.ch, http://www.phys.ethz.ch/~franklin/