package file format:
<packagename>-<s|c><kryptos version>-<version>.kpkg
ex:
apache-s1-2.0.123.kpkg
contains an xml file like so:
<?xml version='1.0'>
<kpkg version='1.0' xmlns='http://kr4z.com/blabla'>
<info>
<id>apache</id>
<name>Apache</name>
<version>2.0.123</version>
<pkgversion>1</pkgversion>
<type>source</type>
<description>Apache is a http server bla bla bla...</description>
<script type="text/javascript">install.js</script>
<dependiences>
<parent>kryptbase</parent>
<children>apache</children>
<provides>
<provide>
<versions></versions>
<id>httpd</id>
</provide>
</provide>
<depends>
<group>
<depend type="install">
<versions></versions>
<id>gcc</id>
</depend>
<depend type="install">
<versions></versions>
<id>icc</id>
</depend>
</group>
<depend type="run">glibc</depend>
</depends>
</dependiences>
</info>
<contents type="compressed/gzip">
kh4b4w356345^#$%#$%TGWegwbee/6u/67[i5p6o7[jertgoiw45$%Y$%gwleirugwierb/
45yWTWREbti5utgwoiutgwelrjbgsrfg .x,mfe y@#$Wergwleb werkgnw4ejbtqtwert
WTERKYbl34kjbtlkwerj fvernbq;elrgblregbqliwehaaerERHthn;ltrhnslknfgvjkb
</contents>
</kpkg>
XForms for configuring? And for when configuring after installed?
Allowing config options to change dependances without script
Root package known as
kpkgtop
packages can depend on "kryptlinux" to say that they require this OS
package api must be abstracted enough so that packages can be used on
an OS with an entirely different file structure (my os)
install script:
package.id
package.name
package.version
package.pkgversion
package.type
package.description
package.scriptname
package.parent
package.children
package.provides
package.depends
<script type="text/javascript">
package.onconfigure = configure;
package.onoptionchange = optionchange;
function configure() {
package.options.createNew('docs','Documentation');
}
function optionchange(optionid) {
switch (optionid) {
case 'docs':
package.depends.groups['man'].depend
break;
}
}
</script>