nixo
/
guix-devel
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc: Document the 'upstream-name' property. 

Reported by Hartmut Goebel <h.goebel@crazy-compilers.com>.

* doc/guix.texi (Invoking guix refresh): Document 'upstream-name'.
This commit is contained in:
Ludovic Courtès 2018-02-05 12:13:24 +01:00
parent 76dbb7516e
commit a5e03674d1
No known key found for this signature in database
GPG Key ID: 090B11993D9AEBB5
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/guix.texi
View File

@ -6358,6 +6358,19 @@ are many packages, though, for which it lacks a method to determine
whether a new upstream release is available. However, the mechanism is whether a new upstream release is available. However, the mechanism is
extensible, so feel free to get in touch with us to add a new method! extensible, so feel free to get in touch with us to add a new method!
Sometimes the upstream name differs from the package name used in Guix,
and @command{guix refresh} needs a little help. Most updaters honor the
@code{upstream-name} property in package definitions, which can be used
to that effect:
@example
(define-public network-manager
(package
(name "network-manager")
;; @dots{}
(properties '((upstream-name . "NetworkManager")))))
@end example
When passed @code{--update}, it modifies distribution source files to When passed @code{--update}, it modifies distribution source files to
update the version numbers and source tarball hashes of those package update the version numbers and source tarball hashes of those package
recipes (@pxref{Defining Packages}). This is achieved by downloading recipes (@pxref{Defining Packages}). This is achieved by downloading