Eray Özkural

~~~ $ find pisi -iname '*py' | xargs grep TODO pisi/actionsapi/pisitoolsfunctions.py: #TODO FIXME: use an internal install routine for these pisi/actionsapi/variables.py: # TODO: Eventually we should consider getting these from...

~~~ $ find pisi -iname '*py' | xargs grep TODO pisi/actionsapi/pisitoolsfunctions.py: #TODO FIXME: use an internal install routine for these pisi/actionsapi/variables.py: # TODO: Eventually we should consider getting these from...

Distribute an autogenerated reference manual. Defly needed.

this will take many changes: - [ #64 ] - [ #7 ] required for the next update to corporate2 repo

is kludgey and redundant, should be written to remove urlgrabber dependency.

why not implemented here? :/

Ok, now I remember, we need a tool like pisish that will be like a DBMS shell for accessing PISI db 's! Awesome! 😸

``` $ tests/upgrade.sh /Volumes/Centauri/Users/malfunct/Code/projects/pisi + pisi-cli -Dtmp -E --ignore-build-no build tests/zip/pspec.xml tests/unzip/pspec.xml Outputting packages in the working directory. Building PISI source package: zip Compiling action script Safety switch: the component...

``` $ tests/remoterepo.sh + set -e + echo 'beta functionality test script for testing remote repos' beta functionality test script for testing remote repos ++ pwd + echo 'working directory:'...

another tool called pisi-devel or pisi-script tool for accumulating various developer scripts, could be handy