File:  [NetBSD Developer Wiki] / wikisrc / projects / project / sysinst_pkgs.mdwn
Revision 1.2: download - view: text, annotated - select for diffs
Sun Nov 6 14:48:47 2011 UTC (2 years, 5 months ago) by jmmv
Branches: MAIN
CVS tags: HEAD
Define the per-project category and difficulty at the template level,
instead of manually tagging the project pages.  While doing this, prefix
the tags with "category:" and "difficulty:" to make them easier to
understand.

[[!template id=project

title="Add binary pkg install to sysinst"

contact="""
[tech-pkg](mailto:tech-pkg@NetBSD.org)
"""

mentors="""
[Thomas Klausner](mailto:wiz@NetBSD.org)
"""

category="pkgsrc"
difficulty="medium"
duration="3 months"

description="""
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.
The packages might be simple packages like screen or bigger ones like firefox.
Configuration of the packages is not required to happen in sysinst.

A short overview of the steps involved:

* 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.

* 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).

* 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.

For bonus points (just as last step when the rest works):
* Come up with lists of packages for amd64 to fill a CD or DVD (including the NetBSD base system)
"""
]]

[[!tag gsoc]]

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