Thanks Dennis for your input.
To sum up, in your opinion the proposed approach is clean in terms of
Arch guidelines. You also consider decoupling packages a good thing in
general *provided* there is a sound reason for that. There isn't in your
opinion.
What is important is that I brushed asi
On Thu, Feb 27, 2014 at 06:10:39PM +0100, Nowaker wrote:
> Guys, the goal of this "slanted ranting" (really?) is to propose a
> good solution and make Arch better.
Please refrain from implying that the current state needs being made better in
the first place. This is exactly what we're trying to d
On Thu, 27 Feb 2014 18:10:39 +0100
Nowaker wrote:
> Guys, the goal of this "slanted ranting" (really?) is to propose a good
> solution and make Arch better. Please think out of the box and answer
> one question:
>
> Would a separate netctl-wifi-menu package that depends on dialog,
> wpa_suppl
Guys, the goal of this "slanted ranting" (really?) is to propose a good
solution and make Arch better. Please think out of the box and answer
one question:
Would a separate netctl-wifi-menu package that depends on dialog,
wpa_supplicant and dhcpcd be better or not - and why?
My answer is yes
> Date: Thu, 27 Feb 2014 13:22:50 +0100
> From: enwuk...@gmail.com
> To: arch-general@archlinux.org
> Subject: Re: [arch-general] netctl provides wifi-menu which is unusable
>
>> Have you looked at netctl's optional dependencies?
>
> Of course I have but the
On Thu, Feb 27, 2014 at 03:24:38PM +0100, Simon Thelen wrote:
> I don't consider this nonsense, wifi-menu is not an essential part of
> netctl so dialog shouldn't be in the depends. wifi-menu also isn't
> important enough to receive its own package. I see zero problem with
> wifi-menu remaining a b
On 27/02/14 at 13:22, Nowaker wrote:
> Optdepends are used for software like lighttpd or apache where some optional
> modules may need these optdepends. /usr/bin/wifi-menu is a first class
> citizen of this package, not just some optional module.
wifi-menu isn't so much a "first-class-citizen" as i
On Wed, Feb 26, 2014 at 2:09 PM, arnaud gaboury
wrote:
> On Wed, Feb 26, 2014 at 1:37 PM, arnaud gaboury
> wrote:
>> --
>>>
>>> Now:
>>> * Populate the iptables FORWARD chain to route traffic from your physical
>>> interface to the bridge and back.
>>
>> I missed totally this part of the setup.
> Have you looked at netctl's optional dependencies?
Of course I have but the question is - what is the point of providing a
binary that doesn't work at all without some optdepends?
Optdepends are used for software like lighttpd or apache where some
optional modules may need these optdepends.
9 matches
Mail list logo
