Skip to content

Commit

Permalink
update man page
Browse files Browse the repository at this point in the history
  • Loading branch information
neolynx committed Dec 24, 2024
1 parent 2c3a107 commit 65820cd
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 3 deletions.
2 changes: 1 addition & 1 deletion man/aptly.1
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ aptly looks for configuration file first in \fB~/\.aptly\.conf\fR then in \fB/us
With aptly version 1\.6\.0, yaml configuration with inline documentation is supported and recommended (see \fBdebian/aptly\.conf\fR)\.
.
.P
The legacy json configuration is still supported:
The legacy json configuration is still supported (and also supports comments):
.
.IP "" 4
.
Expand Down
5 changes: 3 additions & 2 deletions man/aptly.1.ronn.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,10 @@ aptly has integrated help that matches contents of this manual page, to get help
aptly looks for configuration file first in `~/.aptly.conf` then in `/usr/local/etc/aptly.conf` and `/etc/aptly.conf`. If no config file found (or they are not readable), a new one is created in the
home directory. If `-config=` flag is specified, aptly would use config file at specified location. Also aptly needs root directory for database, package and published repository storage. If not specified, directory defaults to `~/.aptly/`, it will be created if missing.

With aptly version 1.6.0, yaml configuration with inline documentation is supported and recommended (see `debian/aptly.conf`).
With aptly version 1.6.0, yaml configuration with inline documentation is
supported and recommended (see `debian/aptly.conf`).

The legacy json configuration is still supported:
The legacy json configuration is still supported (and also supports comments):

// vim: : filetype=json
// json configuration file with comments
Expand Down

0 comments on commit 65820cd

Please sign in to comment.