recently added pt and nl translations to the setup. thanks! :)

yet another milestone in the setup: except the translations, it seems that it's ready for 0.4pre1, loading language-specific fonts and gettext works again :)

just a draft about how to re-call a plugin from an other plugin in the setup:

        extern GList *plugin_list;
        int i;
        plugin_t *plugin;
        for (i=0; iname, "loadsource"))
                        plugin->run(config);
        }

here we call the loadsource plugin from an another plugin

now we have git support in darcs (it does not causes any extra dep ;) ), here is a short demo, how does it works:

$ cg-clone http://www.kernel.org/pub/scm/git/git.git

this will fetch a git repo for you, as dr get does not works yet (i don't see if this is planned or not), but then do a

cd git; dr changes --last=5

and it really works fine :)

during coding the setup, i noticed some strange behaviours, i debugged then for a long time ;)

so to learn from my faults:

• strcat does not accepts a NULL pointer as a dest char*
• getenv() just gives you a pointer, you have to strdup() it if you want to modify the value

an other thing: i forgot again and again what's the difference between

step

and

next

in gdb:

• setp executes the current line of the program and stops on the next statement to be executed
• next is like step, however, if the current line of the program contains a function call, it executes the function and stops at the next line

ah, and if you want to execute the whole code line by line from the begining, you'll need

break 1

and then the usual

run

yet another setup update :)

a short TODOlist what have to be done:

• handling package installation errors
• handling category order
• handling possibly required cd changes
• postconf: calling the unchanged *config stuff

everything else seems to be completed! :)

yet another milestone in the setup. the code is ready till the end of partitioning. reach a screenshot here

darcs is not too funny, it's well documented so if you once read the documentation, almost nothing unexpected will happen. but today... i've found a very nice new feature :)

you have a repo. inside the repo there are dirs. some of them are not "dr add"ed. if you run dr rec/what/etc in that dirs, it will find the "partent" repo, and runs the command on it. but you can create a new repo in that not-added dir, and then dr will work on this new repo. nice, eh? :)

what's new in the setup in the last 4 days? see the changes here, basically we ported all the functionality till the end of partitioning. ah, and krix started to work on the (experimental) graphical one :)

krix and me are now working on rewriting the setup script from scratch in c to get a much more robust (plugin based, using a messages bus, etc) installer. you can reach an initial screenshot here