bug#34835: iproute in %base-packages but no matching package

bug#34835: iproute in %base-packages but no matching package

[mikadoZero]

guix describe:
guix 1bc24bb
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: 1bc24bbf00e21a26d9eb71e5c89d941812dcdad7

which iproute:
iproute not found

In system.scm in the definition of %base-packages there is iproute but
if I search for it there is no package with that name.
Output of `guix package -s iproute`:

name: iproute2
version: 4.20.0
outputs: out
systems: x86_64-linux i686-linux armhf-linux aarch64-linux mips64el-linux
dependencies: bdb@6.2.32 bison@3.0.5 flex@2.6.4 iptables@1.6.2 pkg-config@0.29.2
location: gnu/packages/linux.scm:1254:2
homepage: https://wiki.linuxfoundation.org/networking/iproute2
license: GPL 2+
synopsis: Utilities for controlling TCP/IP networking and traffic in Linux  
description: Iproute2 is a collection of utilities for controlling TCP/IP
+ networking and traffic with the Linux kernel.  The most important of these are
+ `ip', which configures IPv4 and IPv6, and `tc' for traffic control.
+ 
+ Most network configuration manuals still refer to ifconfig and route as the
+ primary network configuration tools, but ifconfig is known to behave inadequately
+ in modern network environments, and both should be deprecated.
relevance: 6

name: ghc-iproute
version: 1.7.5
outputs: out
systems: x86_64-linux i686-linux
dependencies: ghc-appar@0.1.4 ghc-byteorder@1.0.4 ghc-network@2.6.3.6
+ ghc-safe@0.3.17
location: gnu/packages/haskell.scm:2834:2
homepage: https://www.mew.org/~kazu/proj/iproute/
license: Modified BSD
synopsis: IP routing table  
description: IP Routing Table is a tree of IP ranges to search one of them on the
+ longest match base.  It is a kind of TRIE with one way branching removed.  Both
+ IPv4 and IPv6 are supported.
relevance: 4

bug#34835: iproute in %base-packages but no matching package

[Julien Lepiller]

Le 12 mars 2019 22:48:19 GMT+01:00, mikadoZero <mikadozero@yandex.com> a écrit :
>guix describe:
>guix 1bc24bb
>    repository URL: https://git.savannah.gnu.org/git/guix.git
>    branch: master
>    commit: 1bc24bbf00e21a26d9eb71e5c89d941812dcdad7
>
>which iproute:
>iproute not found
>
>In system.scm in the definition of %base-packages there is iproute but
>if I search for it there is no package with that name.
>Output of `guix package -s iproute`:
>
>name: iproute2
>version: 4.20.0
>outputs: out
>systems: x86_64-linux i686-linux armhf-linux aarch64-linux
>mips64el-linux
>dependencies: bdb@6.2.32 bison@3.0.5 flex@2.6.4 iptables@1.6.2
>pkg-config@0.29.2
>location: gnu/packages/linux.scm:1254:2
>homepage: https://wiki.linuxfoundation.org/networking/iproute2
>license: GPL 2+
>synopsis: Utilities for controlling TCP/IP networking and traffic in
>Linux  
>description: Iproute2 is a collection of utilities for controlling
>TCP/IP
>+ networking and traffic with the Linux kernel.  The most important of
>these are
>+ `ip', which configures IPv4 and IPv6, and `tc' for traffic control.
>+ 
>+ Most network configuration manuals still refer to ifconfig and route
>as the
>+ primary network configuration tools, but ifconfig is known to behave
>inadequately
>+ in modern network environments, and both should be deprecated.
>relevance: 6
>
>name: ghc-iproute
>version: 1.7.5
>outputs: out
>systems: x86_64-linux i686-linux
>dependencies: ghc-appar@0.1.4 ghc-byteorder@1.0.4 ghc-network@2.6.3.6
>+ ghc-safe@0.3.17
>location: gnu/packages/haskell.scm:2834:2
>homepage: https://www.mew.org/~kazu/proj/iproute/
>license: Modified BSD
>synopsis: IP routing table  
>description: IP Routing Table is a tree of IP ranges to search one of
>them on the
>+ longest match base.  It is a kind of TRIE with one way branching
>removed.  Both
>+ IPv4 and IPv6 are supported.
>relevance: 4

iproute2 provides the "ip" command. Try "ip a" for instance to list your devices and addresses. Does it work?

bug#34835: iproute in %base-packages but no matching package

[mikadoZero]

Julien Lepiller writes:

> iproute2 provides the "ip" command. Try "ip a" for instance to list your devices and addresses. Does it work?

That works.  Thank you for explaining that.

bug#34835: iproute in %base-packages but no matching package

[Leo Famulari]

[-- Attachment #1: Type: text/plain, Size: 311 bytes --]

On Tue, Mar 12, 2019 at 05:48:19PM -0400, mikadoZero wrote:
> In system.scm in the definition of %base-packages there is iproute but
> if I search for it there is no package with that name.

The package is named 'iproute2' but the Scheme variable, which is what
%base-packages is a list of, is named 'iproute'.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#34835: iproute in %base-packages but no matching package

[mikadoZero]

Leo Famulari writes:
> The package is named 'iproute2' but the Scheme variable, which is what
> %base-packages is a list of, is named 'iproute'.

Thank you for the clarification.

Is it common for the Scheme variable to be different from the package
name?  What benefit is there to it being different compared to it being
the same?

bug#34835: iproute in %base-packages but no matching package

[Ricardo Wurmus]

mikadoZero <mikadozero@yandex.com> writes:

> Is it common for the Scheme variable to be different from the package
> name?  What benefit is there to it being different compared to it being
> the same?

It is not very common, but sometimes it is necessary (in the case of
“gnu-gettext”), and sometimes it is merely convenient.

--
Ricardo

bug#34835: iproute in %base-packages but no matching package

[mikadoZero]

Ricardo Wurmus writes:

> mikadoZero <mikadozero@yandex.com> writes:
>
>> Is it common for the Scheme variable to be different from the package
>> name?  What benefit is there to it being different compared to it being
>> the same?
>
> It is not very common, but sometimes it is necessary (in the case of
> “gnu-gettext”), and sometimes it is merely convenient.

Thanks