Using Dapty™ as an add-on.
 
Dapty for nerds

Here are some alternate uses for Dapty

Picking single applications from Dapty.

Dapty(tm) is both a collection of software and also a computing environment based on that collection. There are people and situations where one does not wish to switch the whole working environment to Dapty while still wishing to use some Dapty applications of choice.

This can be easily accomplished by running the desired software as follows:

  • make sure you are authenticated to Dapty:
    daptyauth
    or
    clog your-dapty-account@0l.se
  • in a terminal window run
    /coda/0l.se/dapty/gamma + the-application [possibly args as needed]

  • (gamma may be substituted by alpha or beta according to your preferences )

    Note the plus sign with spaces on both sides of it. This plus sign means the default miljo (Dapty environment) and may be substituted by an explicit miljo name like uclibcgcc if you wish to run gcc to build small binaries statically linked against Dapty's uClibc:

    /coda/0l.se/dapty/gamma uclibcgcc gcc -s -o prog prog.c

    Of course you may create an alias or a shell function as a shortcut like the following example:

    rundapty(){ /coda/0l.se/dapty/gamma + "$@"; }

    Then you e.g. can do

    rundapty pysol

    to get a nice collection of solitaire style card games.

    Another useful shortcut might be

    uclibcgcc(){ /coda/0l.se/dapty/gamma uclibcgcc gcc "$@"; }

    Of course you can add Dapty applications into the menus of your preferred evinronment. Just place the commands as described above in the proper menu definition files - depending on what your environment is.

    Yet another method of running Dapty as an addition to your environment is starting a terminal session like

    xterm -e /coda/0l.se/dapty/gamma + sh
    which gives you an X terminal window with a shell, all Dapty programs being available in that session (but not your locally installed programs).

    A more advanced usage.

    If you definitely want to let Dapty programs run your locally installed ones and vice versa, you can do the following (assuming sh syntax) :

      PREPEND_PATH="$PATH" /coda/0l.se/dapty/gamma + the-application [args]

    or

      PREPEND_PATH="$PATH" /coda/0l.se/dapty/gamma + sh

    or even

      PREPEND_PATH="$PATH" /coda/0l.se/dapty/gamma uclibcgcc sh

    The resulting process will have its PATH pointing to Dapty but prepended by your previous value of PATH, supposedly the local one.

    Using APPEND_PATH instead of PREPEND_PATH will put the local PATH after the Dapty one, e.g.

      APPEND_PATH="$PATH" /coda/0l.se/dapty/gamma uclibcgcc sh

    Note that this explicit setting of PATH may break some programs or applications, that's why this usage is in general discouraged.

     
    Copyright © 2012 Aetey Global Technologies AB - Box 7068 - SE-40232 Göteborg Sweden 2016-06gjv81@aetey.se  |  Privacy&Cookies