File:  [NetBSD Developer Wiki] / wikisrc / projects / project / sysinst_pkgs.mdwn
Revision 1.1: download - view: text, annotated - select for diffs
Sun Nov 6 01:59:12 2011 UTC (9 years, 6 months ago) by jmmv
Branches: MAIN
CVS tags: HEAD
Move existing project definitions from projects/gsoc_2011/ to
projects/project/ .

The goal for this reorganization is to remove any knowledge of the projects
classification from the file hierarchy: the classification goes into tags,
and projects indexes automatically list projects based on such tags.

Also, the current gsoc_2011 name was wrong anyway, because GSoC 2011 has
already concluded and projects would have had to move to a gsoc_2012 directory
anyway.

Lastly, yes, "projects/project/*" is slightly redundant.  But I want to keep
the project lists from the projects "database" clearly separated.

This is as proposed in www@.

    1: [[!template id=project
    2: 
    3: title="Add binary pkg install to sysinst"
    4: 
    5: contact="""
    6: [tech-pkg](mailto:tech-pkg@NetBSD.org)
    7: """
    8: 
    9: mentors="""
   10: [Thomas Klausner](mailto:wiz@NetBSD.org)
   11: """
   12: 
   13: duration="3 months"
   14: 
   15: description="""
   16: sysinst, the NetBSD installation tool, should be able to get NetBSD set up with most packages relevant to the end user during the installation step, to make it possible to get a usable system during the initial setup.
   17: The packages might be simple packages like screen or bigger ones like firefox.
   18: Configuration of the packages is not required to happen in sysinst.
   19: 
   20: A short overview of the steps involved:
   21: 
   22: * Improve sysinst so it can list a pkgsummary.gz file on the install media and offer to install a subset of them. There should be a chooser included in sysinst where the user can select the packages they want to install.
   23: 
   24: * There should be some pre-defined sets included with sysinst that define the necessary packages for a Gnome or KDE desktop, so the user just chooses them (possibly just by adding appropriate meta packages to pkgsrc).
   25: 
   26: * Support fetching a pkgsummary file from a remote host (usually ftp.NetBSD.org with useful default PATH for architecture/release, but overridable) and offer installations of packages from there as well.
   27: 
   28: For bonus points (just as last step when the rest works):
   29: * Come up with lists of packages for amd64 to fill a CD or DVD (including the NetBSD base system)
   30: """
   31: ]]
   32: 
   33: [[!tag gsoc]]
   34: [[!tag medium]]
   35: [[!tag pkgsrc]]

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb