| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
The core module list for perl might as well be bundled with genpkg.
The setup script will install it to the proper place. The scrapecore
script will still be included for completeness but shouldn't have to
be used by the user, hopefully.
|
|
Alot of logic was added to allow changing versions
in mods while still preserving the version in the
$_ver custom variable.
|
|
Forgot to rename a reference to $t.
|
|
Adds GENPKGDBG env variable. Set it to prevent genpkg from
removing PKGTREE and PKGDATA.
|
|
This matches the prepkg script name.
|
|
|
|
This takes PKGDATA on standard input printing it to standard
output. Digests for each file entry in the source array are
printed along with the other PKGDATA fields.
|
|
|
|
Updates genpkg as well. Adds func to genpkg for
merging files back together from PKGTREE dir.
|
|
The current setup is only really good for modifying PKGBUILD fields. The
modification of PKGBUILD funcs is hackish. Instead, the tweaks will be
written in a scripting language (like Io) where both PKGBUILD fields
and function code can be easily modified.
Fields should be able to be modified just like arrays, but with easier
package matching going on. PKGBUILD bash functions are simply arrays
of lines, but they are not as sophisticated. Instead they can only be
appended to.
Package files are represented as trees. Each file (PKGBUILD pkg.install)
is a child of the top-level node of the tree. Each child of the file
node is a section of the file (intro, body, end). Each section can
also have its own intro, body, and end node. In this way each bash
function is a node with its own intro, body, and end node. Prepending
to a function appends to its intro node. Appending to a function appends
to its end child node. The body cannot be modified.
|
|
|
|
Use files named PKGDATA instead of files named PKGMETA.
|
|
|
|
|
|
|
