summaryrefslogtreecommitdiffstats
path: root/source-package-format-1.0.txt
diff options
context:
space:
mode:
Diffstat (limited to 'source-package-format-1.0.txt')
-rw-r--r--source-package-format-1.0.txt32
1 files changed, 15 insertions, 17 deletions
diff --git a/source-package-format-1.0.txt b/source-package-format-1.0.txt
index 1af04c7..61728f5 100644
--- a/source-package-format-1.0.txt
+++ b/source-package-format-1.0.txt
@@ -21,26 +21,24 @@ This specification is in draft status. It is a work-in-progress and is subject
to change. Comments and revisions are welcome.
-BACKGROUND AND RATIONALE
-========================
+BACKGROUND
+==========
A source package consists of software source code, a build system, and package
metadata. From it is built one or more binary packages, which can be installed
-into an operating system. These binary packages are managed by a "package
-manager", a program or set of programs that tracks, installs, removes, and
-upgrades software packages on a system.
-
-The package manager we are using is opkg, a small and lightweight package
-manager. Its binary package format resembles that of the dpkg package manager
-used in Debian and Debian-based operating system distrubutions.
-
-Version 1.0 of our source package format is intended to resemble the package
-format of the OpenBricks Embedded Linux Framework. Unlike the OpenBricks
-format, however, this format is designed to support the building of multiple
-binary packages from one source package. Additionally, source packages in this
-format are intended to be maintained independently rather than in one monolithic
-software repository (such as that of OpenBricks). In these and other respects,
-this format draws inspiration from Debian's source package formats.
+into an operating system.
+
+
+RATIONALE
+=========
+
+This source package format is intended to resemble the package format of the
+OpenBricks Embedded Linux Framework. Unlike the OpenBricks format, however,
+this format is designed to support the building of multiple binary packages from
+one source package. Additionally, source packages in this format are intended
+to be maintained independently rather than in one monolithic software repository
+(such as that of OpenBricks). In these and other respects, this format draws
+inspiration from Debian's source package formats.
DIRECTORY STRUCTURE