-- should be faster with rowid due to the blob content
-- these are really just blobs of data
+-- TODO copyright and license information should probably
+-- go here
CREATE TABLE files (
- hash text primary key,
- size integer,
- compression text,
+ hash text primary key, -- sha256 of content
+ size integer, -- bigint? certainly need > 2GB
+ compression text, -- always xz?
content blob
)
;
-- information about packages
-- a package is identified by a package,version,release triple
create table packages (
+ -- primary key columns
package text,
version text, -- the upstream version string
release integer, -- the local release number
+ pkgid text, -- the three above joined with '-'
+
+ -- metadata columns
description text,
architecture text,
url text,
without rowid
;
+-- packagefile hash is columns as text, joined with null bytes, then
+-- sha256 sum of that
+-- package checksum is package columns as text, joined with null bytes,
+-- other than the checksum and install_time column
+-- then that hashed. finally, that hash, plus the ascii sorted
+-- hashes of the package files all joined with newlines, hashed.
+-- really don't like this.
+
-- files contained in a package
create table packagefiles (
-- package id triple
groupname text, -- group of owner
uid integer, -- numeric uid, generally ignored
gid integer, -- numeric gid, generally ignored
- --filetype integer default 0, -- 0 regular file, 1 directory, 2 symlink
- -- regular file if null target and not null hash
- -- except that we could not know the hash, or care
- -- directory if null hash and null target
- -- symlink if null hash and not null target
- -- hard link if not null hash and not null target
- -- device special files add dev number column
- -- fifos add mode? Can encode filetype in mode.
- target text, -- link target for symlinks
+ filetype varchar default 'r',
+ -- r regular file
+ -- d directory
+ -- s symlink
+ -- h hard link -- not supported
+ -- c character special and b device special files add dev number column
+ -- b block special
+ -- p fifos (i.e. pipe)
+ target text, -- link target for links
+ -- device file dev numbers, should probably be a separate table
+ devmajor integer,
+ devminor integer,
hash text, -- null if no actual content, i.e. anything but a regular file
mtime integer, -- seconds since epoch, finer resolution probably not needed
primary key (package,version,release,path),
without rowid
;
+create table pathtags (
+ -- package id triple
+ package text,
+ version text,
+ release integer,
+
+ path text, -- filesystem path
+ tag text,
+ primary key (package,version,release,path,tag)
+)
+without rowid
+;
+
create table elfinfo (
file text, -- hash of blob
elftype text,
"group" text
);
+-- zpm actions
+-- not sure how machine readable this needs to be,
+-- do not at all for now, figure it out later
+-- could be worth logging all commands in a history table,
+-- the zpm driver could do that and capture the exit status
+-- as well
+-- might want the history table to note a "group" to tie together
+-- sub-invocations, probably an environment variable set if not
+-- already set by zpm, probably a uuid or a timestamp
+create table zpmlog (
+ ts integer, -- timestamp of action, may need sub-second
+ action text,
+ target text, -- packagename, repo name, etc
+ info text -- human readable
+);
+
+create table history (
+ ts integer, -- again, probably needs timestamp sub second
+ cmd text,
+ args text,
+ status integer
+);
+
+create table repository (
+ name text primary key, -- our name for a repo
+ url text not null,
+ priority integer not null default 1,
+ refreshed integer -- last refresh time
+);
+
+-- urls for downloading packages. possibly unneeded
+create table repository_packages (
+ repo text,
+ pkg text, -- glob pattern? in which case others not needed
+ version text,
+ release text,
+ url text
+);
+
+-- track which repository a package was cloned from, i.e. where we got it
+create table packagesource (
+ name text,
+ version text,
+ release integer,
+ repository text references repository
+);
+
commit;