On Thu, Sep 25, 2008 at 2:14 PM, Dan McGee wrote:

On Thu, Sep 25, 2008 at 5:37 AM, Ronald van Haren wrote:

...

please signoff for both architectures.

# changes wrt to dhcpcd3 series: August 2008 sees the first release of dhcpcd-4. The new version moves all configuration to /libexec/dhcpcd-run-hooks,

Is this the case in our package? We never use libexec in Arch, so I think we need to do something here.

...

apart from interface address and routing. We also use the same variables as dhclient which means existing custom scripts for dhclient can readily work with dhcpcd with minimal tweaking. Also, the dhcpcd internals have been re-worked around a table setup to extract options directly from the DHCP message instead of populating a custom object and dealing with that. Finally, NetworkManager-0.7.0 works with dhcpcd-4 when built with --with-dhcp-client=dhcpcd. NetBSD -current (4.99.72) imports dhcpcd-4.0.0-rc4 into their base system Smiling

the hooks file location are changed to /usr/libexec in the package.

Ronald

As I said I moved the location to /usr/libexec, so the scheme is like this: dhcpcd /usr/libexec/ dhcpcd /usr/libexec/dhcpcd-hooks/ dhcpcd /usr/libexec/dhcpcd-hooks/01-test dhcpcd /usr/libexec/dhcpcd-hooks/10-mtu dhcpcd /usr/libexec/dhcpcd-hooks/20-resolv.conf dhcpcd /usr/libexec/dhcpcd-hooks/30-hostname dhcpcd /usr/libexec/dhcpcd-run-hooks On my system there is already a kde and maxima directory in /usr/libexec so it seemed a correct location to me. If you think the files should be in another location, let me know and I can get it there. It is an easy fix as I already patched it to go to /usr/libexec instead of /libexec. Ronald

On Thu, Sep 25, 2008 at 3:25 PM, Pierre Schmitz wrote:

Am Donnerstag 25 September 2008 14:32:58 schrieb Ronald van Haren:

...

On my system there is already a kde [..] directory in /usr/libexec

This should not be. Could you check if those files belong to any package?

mmm no they seem not to belong to anything. Maybe a leftover from kde 4.0 alpha packages I once had installed -->> removed them. I see the libexec files for kde4 now live in /usr/lib/kde4/libexec. Maybe I should use this same scheme for dhcpcd, so they go into /usr/lib/dhcpcd/libexec. If nobody objects to that I will do a -3 version in a couple of hours. Ronald

On Thu, Sep 25, 2008 at 9:33 AM, Allan McRae wrote:

Given there will be nothing else in that directory, /usr/lib/dhcpcd/ will be fine.

Agreed. We should use /usr/lib for this stuff. I, for one, would be fine with just using /usr/lib/ as the prefix. Allan's proposal would make the path: /usr/lib/dhcpcd/dhcpcd-hooks/, but it's your decision. Eeek, just noticed that dhcpcd-run-hooks is a binary, so Allan's proposal is actually probably the best for this. I would assume there is a --libexec-dir param for this?

Some packages do create files in {/usr,}/libexec. My problem with storing them anywhere under /usr is that you might be mounting /usr and need network before that. On 9/25/08, Dan McGee wrote:

On Thu, Sep 25, 2008 at 5:37 AM, Ronald van Haren wrote:

...

please signoff for both architectures.

# changes wrt to dhcpcd3 series: August 2008 sees the first release of dhcpcd-4. The new version moves all configuration to /libexec/dhcpcd-run-hooks,

Is this the case in our package? We never use libexec in Arch, so I think we need to do something here.

...

apart from interface address and routing. We also use the same variables as dhclient which means existing custom scripts for dhclient can readily work with dhcpcd with minimal tweaking. Also, the dhcpcd internals have been re-worked around a table setup to extract options directly from the DHCP message instead of populating a custom object and dealing with that. Finally, NetworkManager-0.7.0 works with dhcpcd-4 when built with --with-dhcp-client=dhcpcd. NetBSD -current (4.99.72) imports dhcpcd-4.0.0-rc4 into their base system Smiling

the hooks file location are changed to /usr/libexec in the package.

Ronald

-- Sent from Gmail for mobile | mobile.google.com