it's a mix of a dynamic and static system, by that i mean

the [<arch_repo>::<year><month><day>], i'll just call it repo structure

is realised by symlinks, the repo is sync via rsync

and then a 10 line? script moves some files around

....

i'm not too sure yet how the security patched pkgs will be done,

i wanted to do it this wasy as well, but am not sure about the effects of having os many symlinks

if i don't go that way

then it will be provided by the dynamic system

probably implemented in php as i don't wanna mess with settign up python(it would also mean if i change server there might be problems)

the arms(script) as i'll call it, will simply lookup the pkg/filename in a database and redirect

so pacman will request arm.kh.nu/arms/pacman-3.2.0-1.pkg.tar.gz and it will redirect you to /core/os/i686/pac~ for example

this will be the basis for allowing to sync back by simply changing the mirror

so you set the mirror to /arms/history/2008-8-18 for example and it redirects pacman, or your browser to /core,extr~/os~

......

i should point out that the files are kept in their respective repos

so they other scripts or whatever can interact with them

.....

long story short

arm.kh.nu/core::2008-8-18 is a symlink to arm.nrk.cc/core

and all the pkgs are where they'd otherwise be (a huge mess, i know)

------------------------------------------------------------------------------------------------------------------------

first feature of `arms`::

list the pkgs that were there on a certain day

currently if u visit the site, u simply get a directory list

--------

p.s thanks for all your support and idea

Last edited by kumyco (2009-05-22 19:41:17)