Projects/KDE on Windows/Issues/emerge - Revision history

Jstaniek at 10:25, 16 July 2008

2008-07-16T10:25:33Z

Jstaniek: /* Junior Jobs */

2008-01-30T23:00:40Z

‎Junior Jobs

Jstaniek: /* Junior Jobs */

2008-01-30T23:00:28Z

‎Junior Jobs

Jstaniek at 22:59, 30 January 2008

2008-01-30T22:59:54Z

Jstaniek at 22:37, 30 January 2008

2008-01-30T22:37:59Z

Jstaniek at 22:37, 30 January 2008

2008-01-30T22:37:49Z

Jstaniek at 22:36, 30 January 2008

2008-01-30T22:36:44Z

Jstaniek at 10:04, 25 January 2008

2008-01-25T10:04:11Z

SaroEngels at 19:11, 7 January 2008

2008-01-07T19:11:34Z

SaroEngels: emerge thoughts

2008-01-06T23:13:58Z

emerge thoughts

New page

Issues with emerge:
for system dependent parts emerge should rely on the kdewin-installer package
*make the kdewin-installer work on the commandline and integrate into emerge
*integrate kdewin-menubuilder
*test for kdewin-* applications before using them

Some more functions that are needed:
*find a better solution what to build (accept multiple targets at the commandline like the original emerge does)
*implement an update command which either updates the installed packages or which updates one package only
*make two packages possible: 'emerge-bin' and 'emerge-portage'.
*use another way to update the portage directory in future (rsync or similar)

@@ Line 14: / Line 14: @@
 === Add missing documentation ===
 There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
 [[Category:MS Windows]]

@@ Line 12: / Line 12: @@
 == Junior Jobs ==
-;Add missing documentation:There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
+=== Add missing documentation ===
 [[Category:MS Windows]]

@@ Line 12: / Line 12: @@
 == Junior Jobs ==
-*There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
+;Add missing documentation:There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
 [[Category:MS Windows]]

@@ Line 11: / Line 11: @@
 *use another way to update the portage directory in future (rsync or similar)
-== Junior jobs ==
+== Junior Jobs ==
 *There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
 [[Category:MS Windows]]

← Older revision		Revision as of 22:37, 30 January 2008
Line 13:		Line 13:
	== Junior jobs ==		== Junior jobs ==
	*There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.		*There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
		+
		+	[[Category:MS Windows]]

@@ Line 1: / Line 1: @@
 == Issues with ''emerge'' ==
-for system dependent parts emerge should rely on the kdewin-installer package
+For system-dependent parts emerge should rely on the kdewin-installer package
 *make the kdewin-installer work on the commandline and integrate into emerge
 *integrate kdewin-menubuilder
@@ Line 12: / Line 12: @@
 == Junior jobs ==
-* there seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options
+*There seem to be tons of options that were added but not yet documented - if someone has nothing to do or if you want to understand emerge better, you should start and document those options. The options are defined in emerge/bin/emerge.py so you should be able to find them easily.
-The options are defined in emerge/bin/emerge.py so you should be able to find out easily

@@ Line 1: / Line 1: @@
-Issues with emerge:
+== Issues with emerge ==
 for system dependent parts emerge should rely on the kdewin-installer package
 *make the kdewin-installer work on the commandline and integrate into emerge
@@ Line 5: / Line 5: @@
 *test for kdewin-* applications before using them
-Some more functions that are needed:
+== Some more functions that are needed ==
 *find a better solution what to build (accept multiple targets at the commandline like the original emerge does)
 *implement an update command which either updates the installed packages or which updates one package only
 *make two packages possible: 'emerge-bin' and 'emerge-portage'.
 *use another way to update the portage directory in future (rsync or similar)