| 1 |
Hi all! |
| 2 |
|
| 3 |
I have been fiddling around with optparse a lot this weekend and i |
| 4 |
also tried to clean up the package structure. |
| 5 |
I created a working ebuild as well, but I'm not yet using it, since I |
| 6 |
would have to remerge after every commit (and therefore I'd have to |
| 7 |
make commits _all the time_) |
| 8 |
|
| 9 |
I was wondering what the best way to parse the input would be.. |
| 10 |
started out with -I, -U etc... but I think the best solution now is: |
| 11 |
# ./package-version.py install/upgrade/remove/purge |
| 12 |
or when using the global tool: |
| 13 |
# wacfg install/purge/upgrade/remove package version |
| 14 |
|
| 15 |
The global tool is currently broken due to this change, but will be fixed soon. |
| 16 |
Hopefully I'll get around to put in color-support.. i really like |
| 17 |
color-support :) |
| 18 |
|
| 19 |
|
| 20 |
Also Bene and I have been thinking about a global database, something |
| 21 |
like layman's repo-list, where all the configfiles for the different |
| 22 |
packages could be hosted so that one could even just do: |
| 23 |
wacfg --use-online-repo install wordpress (ommitting a version |
| 24 |
should obviously use the latest) |
| 25 |
|
| 26 |
The problem with this is, however, that this way one can not tell |
| 27 |
portage which dependencies a package has since portage is unaware of |
| 28 |
it. |
| 29 |
The global database is probably something for distros that are not |
| 30 |
that aware of webapps yet - will evaluate that on debian later... |
| 31 |
maybe. |
| 32 |
|
| 33 |
################################################### |
| 34 |
I realized, I completely forgot to mention the git-url last time: |
| 35 |
http://github.com/nutztherookie/wacfg |
| 36 |
################################################### |
| 37 |
Have a look :-) |
| 38 |
|
| 39 |
|
| 40 |
Cheers and have a nice week! |
Archives