[arch-dev-public] iproute2 to base
Is there any reason that iproute2 should not be added to base? It is no longer pulled in since initscripts was removed and moved to extra. And, as far as I can tell there is no easy way to set up a static ip with just the packages that are currently in base. -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
On Mon, Oct 15, 2012 at 7:16 PM, Daniel Wallace <danielwallace@gtmanfred.com> wrote:
Is there any reason that iproute2 should not be added to base? It is no longer pulled in since initscripts was removed and moved to extra. And, as far as I can tell there is no easy way to set up a static ip with just the packages that are currently in base. -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
Makes sense. I'll add it to the 'base' group. Ronald
Am 15.10.2012 20:05, schrieb Ronald van Haren:
On Mon, Oct 15, 2012 at 7:16 PM, Daniel Wallace <danielwallace@gtmanfred.com> wrote:
Is there any reason that iproute2 should not be added to base? It is no longer pulled in since initscripts was removed and moved to extra. And, as far as I can tell there is no easy way to set up a static ip with just the packages that are currently in base. -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
Makes sense. I'll add it to the 'base' group.
Not needed as netcfg already depends on it. -- Pierre Schmitz, https://pierre-schmitz.com
On Mon, Oct 15, 2012 at 08:10:34PM +0200, Pierre Schmitz wrote:
Am 15.10.2012 20:05, schrieb Ronald van Haren:
On Mon, Oct 15, 2012 at 7:16 PM, Daniel Wallace <danielwallace@gtmanfred.com> wrote:
Is there any reason that iproute2 should not be added to base? It is no longer pulled in since initscripts was removed and moved to extra. And, as far as I can tell there is no easy way to set up a static ip with just the packages that are currently in base. -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
Makes sense. I'll add it to the 'base' group.
Not needed as netcfg already depends on it.
-- Pierre Schmitz, https://pierre-schmitz.com netcfg isn't in base either -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology
Am 15.10.2012 20:12, schrieb Daniel Wallace:
Makes sense. I'll add it to the 'base' group.
Not needed as netcfg already depends on it.
-- Pierre Schmitz, https://pierre-schmitz.com netcfg isn't in base either
As I pointed out recently, it should be.
[2012-10-15 20:48:46 +0200] Thomas Bächler:
Am 15.10.2012 20:12, schrieb Daniel Wallace:
Makes sense. I'll add it to the 'base' group.
Not needed as netcfg already depends on it.
netcfg isn't in base either
As I pointed out recently, it should be.
Possibly, but regardless of what we end up doing with netcfg, iproute2 should be in base in its own right. -- Gaetan
[2012-10-16 10:50:30 +1100] Gaetan Bisson:
[2012-10-15 20:48:46 +0200] Thomas Bächler:
Am 15.10.2012 20:12, schrieb Daniel Wallace:
Makes sense. I'll add it to the 'base' group.
Not needed as netcfg already depends on it.
netcfg isn't in base either
As I pointed out recently, it should be.
Possibly, but regardless of what we end up doing with netcfg, iproute2 should be in base in its own right.
I just saw you removed wpa_supplicant from the base group too... So if I understand your position correctly you are against individual network connectivity tools being in base, but CLI/GUI using them are fine?!? I mean, why not, but I thought base was supposed to be minimal. -- Gaetan
Am 16.10.2012 03:29, schrieb Gaetan Bisson:
netcfg isn't in base either
As I pointed out recently, it should be.
Possibly, but regardless of what we end up doing with netcfg, iproute2 should be in base in its own right.
I just saw you removed wpa_supplicant from the base group too...
So if I understand your position correctly you are against individual network connectivity tools being in base, but CLI/GUI using them are fine?!? I mean, why not, but I thought base was supposed to be minimal.
There should be some basic network configuration facility installed by default. I feel that adding both netcfg and iproute to base is the right thing to do, but wireless should be optional. I removed wpa_supplicant because it was incredibly inconsistent to have it, but not netcfg. Now they switched roles. I am fine with add wpa_supplicant, iw and crda to base if we really want wireless support installed by default.
[2012-10-16 10:51:34 +0200] Thomas Bächler:
There should be some basic network configuration facility installed by default. I feel that adding both netcfg and iproute to base is the right thing to do, but wireless should be optional.
I removed wpa_supplicant because it was incredibly inconsistent to have it, but not netcfg. Now they switched roles.
I am fine with add wpa_supplicant, iw and crda to base if we really want wireless support installed by default.
Wireless has become widespread to the point that it's all you have in certain places such as airport or hotels. So, yes, in my opinion wireless connectivity tools really do belong in base. -- Gaetan
Le 2012-10-16 09:23, Gaetan Bisson a écrit :
[2012-10-16 10:51:34 +0200] Thomas Bächler:
There should be some basic network configuration facility installed by default. I feel that adding both netcfg and iproute to base is the right thing to do, but wireless should be optional.
I removed wpa_supplicant because it was incredibly inconsistent to have it, but not netcfg. Now they switched roles.
I am fine with add wpa_supplicant, iw and crda to base if we really want wireless support installed by default. Wireless has become widespread to the point that it's all you have in certain places such as airport or hotels. So, yes, in my opinion wireless connectivity tools really do belong in base.
I have no objection to add netcfg, but please keep wpa_supplicant in base. Stéphane
participants (6)
-
Daniel Wallace
-
Gaetan Bisson
-
Pierre Schmitz
-
Ronald van Haren
-
Stéphane Gaudreault
-
Thomas Bächler