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 <dpmcgee@gmail.com> wrote:
On Thu, Sep 25, 2008 at 5:37 AM, Ronald van Haren <pressh@gmail.com> 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