|
| 1 | +# Aptitude Module |
| 2 | + |
| 3 | +The JWSTF Aptitude module is the Linux package-management integration for the Ubuntu Grand / US House software lifecycle. |
| 4 | + |
| 5 | +## Reference source |
| 6 | + |
| 7 | +The module references the Aptitude-related source and project conventions in: |
| 8 | + |
| 9 | +`https://github.com/mearvk/Ubuntu.Determinant.Beta.Restricted` |
| 10 | + |
| 11 | +The source repository is treated as the upstream project reference; this repository does not copy or claim ownership of unrelated Aptitude source code. |
| 12 | + |
| 13 | +## Purpose |
| 14 | + |
| 15 | +Aptitude provides a controlled interface for Debian/Ubuntu package discovery and lifecycle operations. It is the preferred package-management adapter when the host is Debian/Ubuntu and `aptitude` is available. |
| 16 | + |
| 17 | +The module exposes the common JWSTF lifecycle: |
| 18 | + |
| 19 | +```text |
| 20 | +install → update → verify → remove |
| 21 | +``` |
| 22 | + |
| 23 | +and supports: |
| 24 | + |
| 25 | +- package search |
| 26 | +- package installation |
| 27 | +- package update |
| 28 | +- package removal |
| 29 | +- package status / verification |
| 30 | +- dependency-aware planning |
| 31 | +- dry-run/review before material changes |
| 32 | +- provenance capture for package name, version, repository, and operation |
| 33 | +- integration with the graphical installer |
| 34 | +- `/user` and `/deck` deployment profiles without overriding Debian filesystem conventions |
| 35 | + |
| 36 | +## Safety model |
| 37 | + |
| 38 | +The adapter must prefer the native package manager over downloading arbitrary `.deb` files. Persistent or destructive operations must be visible to the caller and require the normal authorization available to the host environment. |
| 39 | + |
| 40 | +`remove` means package-managed removal. It does not delete source repositories or unrelated user data unless the native package operation explicitly defines that behavior and the user authorizes it. |
| 41 | + |
| 42 | +## Tomcat / Apache relationship |
| 43 | + |
| 44 | +For Debian/Ubuntu hosts, Aptitude should be used when installing distribution-managed Apache or Tomcat packages. In that case their normal locations and service units remain authoritative, for example: |
| 45 | + |
| 46 | +- Apache configuration: `/etc/apache2` |
| 47 | +- Apache document root: `/var/www/html` |
| 48 | +- Apache logs: `/var/log/apache2` |
| 49 | +- Tomcat configuration: `/etc/tomcat10` |
| 50 | +- Tomcat state: `/var/lib/tomcat10` |
| 51 | + |
| 52 | +A manually managed Tomcat installation under `/opt/tomcat` is a separate deployment mode and must not be mixed with the package-managed Tomcat tree. |
| 53 | + |
| 54 | +## Integration contract |
| 55 | + |
| 56 | +The JavaFX installer can call this module for Debian/Ubuntu operations while displaying the proposed package changes first. Verification should report the installed version and package-management state after each operation. |
0 commit comments