pve-manager/aplinfo
Dietmar Maurer 68097d8ca6 update aplinfo.dat
Use latest data from download server.
2015-09-11 08:29:11 +02:00
..
aplinfo.dat update aplinfo.dat 2015-09-11 08:29:11 +02:00
apltest.pl apltest: ignore architecture 2013-07-22 07:27:48 +02:00
Makefile update aplinfo.dat 2015-09-11 08:29:11 +02:00
README.format update appliance info file - (use lxc compatible templates) 2015-07-01 13:47:35 +02:00
release@turnkeylinux.com.pubkey implement template download 2012-02-21 11:45:30 +01:00
support@proxmox.com.pubkey imported from svn 'pve-manager/pve2' 2011-08-23 07:40:22 +02:00

PVE Package description format
==============================

We basically use a debian like format - see:

http://www.debian.org/doc/debian-policy/ch-controlfields.html

The following (debian) field are used:

Package, Section, Version, Maintainer, Description

Additionally we define the following fields:

Type: openvz | qemu | lxc
OS: Operating system type
Location: download url
Infopage: url to additional info
ManageUrl: url to connect to management interface
md5sum: md5sum of the package

Here is an example:

Package: proxmox-mailgateway
Version: 2.4-2
Type: openvz
OS: debian-4.0
Section: mail
Certified: yes
Maintainer: Proxmox Support Team <support@proxmox.com>
Location: http://download.proxmox.com/appliances/mail/debian-4.0-proxmox-mailgateway_2.4-2_i386.tar.gz
Infopage: http://pve.proxmox.com/wiki/Proxmox_Mail_Gateway
ManageUrl: https://__IPADDRESS__/
md5sum: 3b48ffe08347229a854bc8d5ee161e1f
Description: Proxmox Mail Gateway
  A full featured mail proxy for spam an virus filtering.


The filename is automatically generated from the above description:

${OS}-${Package}_${VERSION}_i386.tar.gz

If ${Package} starts with "${OS}-", the filename is:

${Package}_${VERSION}_i386.tar.gz