Lars Vogdt wrote:
Hi all
Refering to: http://www.opensuse-education.org/mantis/view.php?id=70
it looks like we've too many packages which are installed per default if a user adds the openSUSE-Education Add on (repository or DVD is the same).
I like to give a short explanation about the current structure and the "magic" behind the patterns. -----------------------------------[edu-pattern] We currently have the following entry in the content file of the repository: RECOMMENDS pattern:education-full ^^^ this line adds the pattern file with the same name into the software proposal of YaST.
you can find that pattern in the directory suse/setup/descr/ in the repository (with 11.0 the format changes and all pattern files are pasted together to one gzip'ed pattern file, so have a look at the 10.2 or 10.3 pattern to get the example: http://www.opensuse-education.org/download/repo/1.0/10.2/suse/setup/descr/ed...
You can see: this pattern file _Req_uires the x11 pattern and _Rec_ommends three edu-patterns: education-desktop kids-education-desktop youth-education-desktop
Now an overview about the current patterns: 1) education-desktop => Software which can be used in educational enviroments on client site. - kiosktool - sabayon - italc ^^^ generic packages which makes the live of an administrator or teacher easier in schools.
2) kids-education-desktop => Software for small kids (4-10 years) which can be used in educational enviroments on client site. - gcompris - childsplay - pysycache - ... ^^^ "real" packages for the kids
3) youth-education-desktop => Software for youths (11-14 years) which can be used in educational enviroments on client site. - LabPlot - audacity - bluefish - ... ^^^ "real" packages for older children
We also have two patterns for server applications right now: - edu-server - kiwi-ltsp ^^^ those patterns are NOT selected by default. People who try to setup a server have to select them manually.
All pattern files are created as normal RPM packages and are "developed" using Subversion and a simple directory and file structure. So neither adding packages nor translating the descriptions is a big deal.
Some examples and information can be found here: http://en.opensuse.org/Education/Development#The_development_of_pattern_file...
-----------------------------------[/edu-pattern]
So I want to ask for help!
* Please provide some new proposals how we can split the current patterns into smaller parts. * Which patterns and packages should be installed per default? * Which packages should be suggested ?
With kind regards, Lars
Lars and the Team, It is great that we are able to "build" so much software for the Education repository. Great work and Thanks to all of you! Now we need to create a real product. I had always thought that we could add questions to the YaST installer to make the "add-on" more useful to school IT people and parents. I would like to suggest that we separate the repository into "folders" that represent the install environments|patterns and age groups already defined (see above) then if it's possible "inject" questions into the existing YaST module or create a new YaST installer for the add-on DVD to install these groups. I'm thinking that putting the DVD into an already running system could "autorun" a web page that contains "One-Click" YMP's and the pattern descriptions. (could this module also figure out which desktop is used and exclude KDE only packages on a Gnome machine or vice versa?) . When installing the OS on a machine, choosing the ADD-ON media and inserting the disk would add a few extra questions to the YaST installer that are the same choices as the YMP's in the autorun. example- Thanks for choosing the openSUSE Education ADD-On! Do you want to build an : education-server y or n kids-education-desktop designed for children ages 4-10 y or n youth-education-desktop designed for children ages 11-14 y or n secondary education-desktop designed for ages 15 - adult y or n Do you want classroom management tools? y or n I believe that the desktop\classroom management tools such as italc should be offered as an individual choice. I don't think it's necessary for us subdivide the groups beyond basic age and desktop. Do we need to create a wiki page that includes a spreadsheet\table that allows us to separate the packeages? example title, gnome, kde, 4-10, 11-14, 15-adult. tuxpaint,yes, , yes, , then we can know for sure which packages to include in each group. -- To unsubscribe, e-mail: opensuse-edu+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-edu+help@opensuse.org