Remove two projects that are done.
Submitted by: pav
This commit is contained in:
Robert Watson
parent
752a2c7820
commit
5fceb6f31d
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=33937
1 changed files with 1 additions and 104 deletions
|
|
@ -15,7 +15,7 @@ Ideas//EN"
|
|||
<ideas>
|
||||
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
|
||||
<cvs:keyword name="freebsd">
|
||||
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.106 2009/03/12 14:33:29 kib Exp $
|
||||
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.107 2009/03/12 14:52:07 pgj Exp $
|
||||
</cvs:keyword>
|
||||
</cvs:keywords>
|
||||
|
||||
|
|
@ -1116,73 +1116,6 @@ destDir parameter.</li>
|
|||
</desc>
|
||||
</idea>
|
||||
|
||||
<idea id="ports-collect-messages">
|
||||
<title>Collect the pkg-message output</title>
|
||||
|
||||
<desc>
|
||||
<p><strong>Technical contact</strong>: <a
|
||||
href="mailto:pav@FreeBSD.org">Pav Lucistnik</a></p>
|
||||
|
||||
<p>Collect the pkg-message output of dependencies and print them together
|
||||
after the whole build finishes.</p>
|
||||
|
||||
<p>Details: Change the current ad-hoc way of including pkg-message in
|
||||
the stdout of the build process. Automatically display pkg-message
|
||||
in post-install, if present. For the dependencies, save the copies
|
||||
of pkg-messages, as displayed in post-install, in /var/db/pkg, and
|
||||
display them collectively once the whole build finishes. Also
|
||||
allow for manual review by user later (new flag to
|
||||
pkg_info(1)).</p>
|
||||
|
||||
<p><strong>Requirements:</strong></p>
|
||||
|
||||
<ul>
|
||||
<li>Knowledge of shell and make coding, and basic overview of how
|
||||
ports works.</li>
|
||||
<li>Basic knowledge of C.</li>
|
||||
</ul>
|
||||
|
||||
</desc>
|
||||
</idea>
|
||||
|
||||
<idea id="ports-options">
|
||||
<title>Improvements of OPTIONS</title>
|
||||
|
||||
<desc>
|
||||
<p>The current OPTIONS infrastructure can be improved in several ways.</p>
|
||||
<ul>
|
||||
<li>It should be possible to define OPTIONS after bsd.ports.pre.mk.</li>
|
||||
<li>Add an API to override the current curses based interface with
|
||||
a different GUI, e.g. zenity/gdialog instead of dialog.</li>
|
||||
<li>More room for a description in the OPTIONS dialog - possibly some
|
||||
sort of help dialog could be provided for each option, like in
|
||||
sysinstall.</li>
|
||||
<li>Better handling of cases where OPTIONS are changed/added/removed
|
||||
between upgrades.</li>
|
||||
<li>The ability to depend on, or at least test, OPTIONS set in other
|
||||
ports. Possibly it would be nice to enforce setting variables that are
|
||||
depended upon when the port is being installed as a dependency.</li>
|
||||
<li>Other types of OPTIONS controls - A text box in particular would be
|
||||
useful for entering variables that need real values.</li>
|
||||
<li>The possibility for mutually exclusive OPTIONS.</li>
|
||||
<li>Bugfixes:
|
||||
<ul>
|
||||
<li>If you attempt to run make config for a port with
|
||||
${PKGNAMEPREFIX} defined, the make config process will error out
|
||||
with:<br/>
|
||||
===> Using wrong configuration file /path/options/file<br/>
|
||||
The solution is to define LATEST_LINK to be prefix-${PORTNAME},
|
||||
but this should be done internally.</li>
|
||||
</ul></li>
|
||||
</ul>
|
||||
<p><strong>Requirements</strong>:</p>
|
||||
<ul>
|
||||
<li>Strong knowledge of shell and make code.</li>
|
||||
<li>A basic understanding of the inner workings of the ports tree.</li>
|
||||
</ul>
|
||||
</desc>
|
||||
</idea>
|
||||
|
||||
<idea id="ports-pkgtools">
|
||||
<title>Package tools improvements</title>
|
||||
|
||||
|
|
@ -1234,42 +1167,6 @@ destDir parameter.</li>
|
|||
</desc>
|
||||
</idea>
|
||||
|
||||
<idea id="ports-upgrade">
|
||||
<title>Utility for safe updating of ports in base system</title>
|
||||
|
||||
<desc>
|
||||
<p>Also known as <em>rewrite portupgrade in C</em>.</p>
|
||||
|
||||
<p>Write a new utility for the pkg_install suite, possibly named
|
||||
pkg_upgrade(1), implementing a subset of existing portupgrade
|
||||
functionality. The required functionality is:</p>
|
||||
|
||||
<ul>
|
||||
<li>fixing @pkgdep records in +CONTENTS file</li>
|
||||
<li>fixing +REQUIRED_BY records</li>
|
||||
<li>storing old copies of shared libraries after shmajor number
|
||||
change in /usr/local/lib/compat/pkg</li>
|
||||
<li>upwards and downwards recursive modes</li>
|
||||
<li>ability to work on a complete local ports tree without valid
|
||||
INDEX file</li>
|
||||
<li>ability to work on a remote (ftp) package set without local
|
||||
ports tree</li>
|
||||
</ul>
|
||||
|
||||
<p>Anything that existing portupgrade can do is a desired
|
||||
functionality. It would be nice to be command line compatible with
|
||||
portupgrade, but it's not a requirement.</p>
|
||||
|
||||
<p><strong>Requirements</strong>:</p>
|
||||
|
||||
<ul>
|
||||
<li>Basic understanding of the Ports Collection design.</li>
|
||||
<li>Good skills writing C code.</li>
|
||||
<li>Ability to read Ruby will help.</li>
|
||||
</ul>
|
||||
</desc>
|
||||
</idea>
|
||||
|
||||
<idea id="ports-license-audit" class="soc2008">
|
||||
<title>Ports license auditing infrastructure</title>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue