[Midnightbsd-cvs] www [573] trunk/documentation/mports/index.html: this documentation in mport is REALLY OLD.
laffer1 at midnightbsd.org
laffer1 at midnightbsd.org
Sat Nov 22 13:51:27 EST 2014
Revision: 573
http://svnweb.midnightbsd.org/www/?rev=573
Author: laffer1
Date: 2014-11-22 13:51:27 -0500 (Sat, 22 Nov 2014)
Log Message:
-----------
this documentation in mport is REALLY OLD. Update for subversion, the license options, etc.
Modified Paths:
--------------
trunk/documentation/mports/index.html
Modified: trunk/documentation/mports/index.html
===================================================================
--- trunk/documentation/mports/index.html 2014-11-22 18:29:12 UTC (rev 572)
+++ trunk/documentation/mports/index.html 2014-11-22 18:51:27 UTC (rev 573)
@@ -46,11 +46,10 @@
<h3 id="s2a">Using mports</h3>
<p>You can install mports during the installation of MidnightBSD. If you forgot to do so, you may download
- the latest mports by using <em>cvsup</em> or <em>cvs</em>. Execute the command <br />cvsup /usr/share/examples/cvsup/mports-supfile<br />
- to download the mports. Alternatively, you can use <br />
- mkdir /usr/mports<br />
+ the latest mports by using <em>svn</em>. You can use <br />
cd /usr<br />
- cvs -z 7 -d anoncvs at stargazer.midnightbsd.org:/home/cvs co mports</p>
+ svn co http://svn.midnightbsd.org/svn/mports/trunk mports
+</p>
<p>Updating mports periodically is recommended. New versions of software and additional software are added all the time.
Keeping up to date will help you maintain best security practices and possibly give you new features
@@ -68,9 +67,8 @@
<p>To uninstall a port, simply goto the directory of the mport and type make deinstall</p>
- <p>There are also utilities like pkg_add, pkg_delete and so forth included in the base system. pkg_add -r portname can fetch a
- precompiled package from the MidnightBSD server and install it for you. You can also install your own packages. There are many
- possibilities.</p>
+ <p>If you prefer to use packages, consult the mport command. It can install packages via mport install or remove
+ packages via mport delete. You can use mport list to see what is currently installed.</p>
<h3 id="s3a">History</h3>
@@ -104,15 +102,123 @@
See the <a href="policy.html">policy page</a> for information on current port standards.</p>
<p>MidnightBSD introduced the LICENSE variable years before FreeBSD's new LICENSE framework for ports. We got the idea from
-some of the other BSD projects. Our system does not handle multiple license types as yet (we have an agg type), and ours is
-indexed into the build cluster software so that our mport tools can later display licensing information with
-<code>mport info <i>pkgname</i></code>.
+some of the other BSD projects. Until 2014, mports did not handle multiple license types, but rather we set
+agg to indicate it was under several liceness. Licenses are
+indexed into the build cluster software so that mport tools can later display licensing information with
+<code>mport info <i>pkgname</i></code>. License is also used to exclude files during the "bless" of
+a magus run from the FTP server.
</p>
+
+<p>FreeBSD introduced support for multiple licenses (both dual license and aggregate/multi)
+with their ports tree. Recently, we added preliminary support for this to mport tools and
+mports.</p>
+
+<table>
+<thead>
+<caption>User Configurable License Settings (/etc/make.conf)</caption>
+ <tr>
+ <th>Variable</th>
+ <th>Description</th>
+ </tr>
+</thead>
+<tbody>
+<tr>
+<td><p><tt>LICENSES_ACCEPTED</tt> </p></td>
+ <td><p > Accepted licenses </p></td>
+</tr>
+<tr>
+<td><p > <tt >LICENSES_GROUPS_ACCEPTED</tt> </p></td>
+ <td><p > Accepted groups </p></td>
+</tr>
+<tr>
+<td><p > <tt >LICENSES_REJECTED</tt> </p></td>
+ <td><p > Rejected licenses </p></td>
+</tr>
+<tr>
+<td><p > <tt >LICENSES_GROUPS_REJECTED</tt> </p></td>
+ <td><p > Rejected groups </p></td>
+</tr>
+<tr>
+<td><p > <tt >LICENSES_ASK</tt> </p></td>
+ <td><p > Require explicit user agreement for licenses accepted by default, for example most common licenses in <tt >bsd.licenses.db.mk</tt> </p></td>
+</tr>
+<tr> <td><p > <tt >NO_LICENSES_DIALOGS</tt> </p></td>
+ <td><p > Disable dialog menus (GUI), and use the text interface </p></td>
+</tr>
+<tr> <td><p > <tt >NO_LICENSES_INSTALL</tt> </p></td>
+ <td><p > Disable installation of (all) license files. These will possibly be required for future features (specially scripts or tools outside the ports systems). </p></td>
+</tr>
+</tbody></table>
+
+<table>
+<thead>
+<caption>Port License Settings (Single License)</caption>
+ <tr>
+ <th>Variable</th>
+ <th>Description</th>
+ </tr>
+</thead>
+<tbody>
+<tr> <td><p > <tt >LICENSE</tt> </p></td>
+ <td><p > Code of license (short name; only letters, numbers and underscore) </p></td>
+</tr>
+<tr> <td><p > <tt >LICENSE_PERMS</tt> </p></td>
+ <td><p > Permissions (see below) </p></td>
+</tr>
+<tr> <td><p > <tt >LICENSE_GROUPS</tt> </p></td>
+ <td><p > Groups the license belongs to </p></td>
+</tr>
+<tr> <td><p > <tt >LICENSE_NAME</tt> </p></td>
+ <td><p > Full license name (for the reports) </p></td>
+</tr>
+<tr> <td>p > <tt >LICENSE_FILE</tt> </p></td>
+ <td><p > Full path to license (or use <tt >LICENSE_TEXT</tt>) </p></td>
+</tr>
+<tr> <td><p > <tt >LICENSE_TEXT</tt> </p></td>
+ <td><p > Text to use as a license, for referencing when not available </p></td>
+</tr>
+<tr> <td><p > <tt >LICENSE_DISTFILES</tt> </p></td>
+ <td><p > Name of licensed files (defaults to <tt >${_DISTFILES}</tt>) </p></td>
+</tr>
+</tbody></table>
+
+ <table>
+ <thead>
+<caption>LICENSE_PERMS settings</caption>
+ <tr>
+ <th>Variable</th>
+ <th>Description</th>
+ </tr>
+</thead>
+ <tbody><tr> <td><p > <strong>Variable</strong> </p></td>
+ <td><p > <strong>Description</strong> </p></td>
+</tr>
+<tr> <td><p > <tt >dist-mirror</tt> </p></td>
+ <td><p > Free redistribution of distfile (like FTP mirroring; opposite of <tt >RESTRICTED</tt>) </p></td>
+</tr>
+<tr> <td><p > <tt >dist-sell</tt> </p></td>
+ <td><p > Selling of distfile (like in CD-ROM; opposite of <tt >NO_CDROM</tt>) </p></td>
+</tr>
+<tr> <td><p > <tt >pkg-mirror</tt> </p></td>
+ <td><p > Free redistribution of package (like FTP upload; opposite of <tt >NO_PACKAGE</tt>) </p></td>
+</tr>
+<tr> <td><p > <tt >pkg-sell</tt> </p></td>
+ <td><p > Selling of package (like in CD-ROM; opposite of <tt >NO_CDROM</tt>) </p></td>
+</tr>
+<tr> <td><p > <tt >auto-accept</tt> </p></td>
+ <td><p > If present the license is accepted by default, without agreement (at least <tt >LICENSES_ASK</tt> is defined by the user) </p></td>
+</tr>
+</tbody></table>
+ <p>Note that permissions can be denied by prefixing no-, for example no-dist-sell.</p>
+
+ <p>LICENSE_COMB is set to define multi or dual license. This replaces our old approach of using agg. Ports should
+ be updated to reflect this change.</p>
+
<h3 id="s4a">Future Directions</h3>
<ul>
- <li>A new package scheme is early planning. It would be based on FreeBSD's package system, but have several new features
+ <li>A new package scheme is under active development. It would be based on FreeBSD's package system, but have several new features
such as support for bundled packages (several packages in one package), cryptographically signed packages, native option support,
and a radically improved package database using sqlite3 as a backend. (libmport)</li>
@@ -127,8 +233,9 @@
<p>The libmport and mport tools were imported into 0.3-CURRENT for testing. As of 0.4-CURRENT (os version 4004), mport tools support
fetching packages, updating, upgrade of all system packages, deleting packages, listing packages needing to be updated, search, and info on
-a package. The new system will allow us to update packages after a release. Discussion on generating new packages or branching the mports
-tree to only provide security updates has yet to occur.</p>
+a package. The new system will allow us to update packages after a release.
+As of 0.5, the default package manager is mport. Please consult the man page for more information.
+</p>
<div id="disqus_thread"></div>
<script type="text/javascript">
More information about the Midnightbsd-cvs
mailing list