diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html b/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html new file mode 100644 index 000000000..b54488226 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101218/f6b268c4/attachment.html @@ -0,0 +1,35 @@ +A wizard sounds like a good idea....<br><br>are there any howtos on Wizards for M??<br><br>greetings, sascha<br><br><div class="gmail_quote">2010/12/18 Michael scherer <span dir="ltr"><<a href="mailto:misc@zarb.org">misc@zarb.org</a>></span><br> +<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Sat, Dec 18, 2010 at 10:03:36AM +0100, SaschaS wrote:<br> +> So I see basically that we need a guidline on how mageia deals with Spinoffs<br> +> first.<br> +><br> +> If all task are in the repos, I can understand those who say that there are<br> +> to many task.<br> +<br> +</div>The problem is not that there is too much more than the consequence of the<br> +high number of task-*.<br> +<br> +rpmdrake, who is the main consumer of task-* rpm<br> +convention, show all of them as 1 single list. So basically, with lots of tasks-<br> +rpm, you just have a big unsorted list of category. Obviously not good for endusers.<br> +<br> +While it would be useful to group task into sound category, for the moment,<br> +we cannot. One way would be to encode this information in the name ( ie, decide<br> +that task-sound-foo and task-sound-bar are part of the sound category ).<br> +<br> +I am not sure that using the name for this is a good idea. It is quite poor,<br> +in term of metadata, and that's still a tree structure, while may a tag based<br> +one may be better ( like Debian do, for example ).<br> +<br> +More ever, it doesn't make much sense to have task-lamp-* task-nagios and task-kde4<br> +at the same level, they are not destined at the same public.<br> +<br> +Not to mention that installing rpm is ust half of the solution, configuration is<br> +the other one. While we can to some extend push configuration in the rpm, there<br> +is some that we cannot do reliably ( like adding a user to a group ).<br> +<br> +So maybe a wizard is a better solution than using a rpm that does magically everything.<br> +<br> +--<br> +<font color="#888888">Michael Scherer<br> +</font></blockquote></div><br> |