-- 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,
-- 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
+
+ -- metadata columns
description text,
architecture text,
url text,
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 packagefiletags (
+ -- 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,