With systemd being the default, we have no simple network management besides dhcp by default. Should we add netcfg to the base group so it is installed by default?
On Sat, Oct 13, 2012 at 11:34 AM, Thomas Bächler thomas@archlinux.org wrote:
With systemd being the default, we have no simple network management besides dhcp by default. Should we add netcfg to the base group so it is installed by default?
We already have dhcpd in base group. We can enable it to configure dhcp.
E.g: systemctl enable dhcpcd@eth0.service
On Sat, Oct 13, 2012 at 11:34 AM, Thomas Bächler thomas@archlinux.org wrote:
With systemd being the default, we have no simple network management besides dhcp by default. Should we add netcfg to the base group so it is installed by default?
I noticed this is now carried out in [testing]. The PKGBUILD is maintained as part of the netcfg source tree (`make pkgbuild`). Shall I push the change for the next netcfg release? The next release will be 3.0 and is due this week for [testing]. The biggest remaining problem with netcfg at this point is the completely outdated wiki. I've got a skeleton for a new wiki page, but it will take time rolling it out.
- Jouke
On Mon, Oct 15, 2012 at 10:11:46PM +0200, Jouke Witteveen wrote:
On Sat, Oct 13, 2012 at 11:34 AM, Thomas Bächler thomas@archlinux.org wrote:
With systemd being the default, we have no simple network management besides dhcp by default. Should we add netcfg to the base group so it is installed by default?
I noticed this is now carried out in [testing]. The PKGBUILD is maintained as part of the netcfg source tree (`make pkgbuild`). Shall I push the change for the next netcfg release? The next release will be 3.0 and is due this week for [testing]. The biggest remaining problem with netcfg at this point is the completely outdated wiki. I've got a skeleton for a new wiki page, but it will take time rolling it out.
- Jouke
The PKGBUILD is necessarily maintained as part of SVN. You're free to maintain a copy in the source tree, but I really wouldn't count on using that for anything more than to create a git build directly from the tree itself (e.g. initscripts and mkinitcpio do this).
d
On Mon, Oct 15, 2012 at 10:17 PM, Dave Reisner d@falconindy.com wrote:
On Mon, Oct 15, 2012 at 10:11:46PM +0200, Jouke Witteveen wrote:
On Sat, Oct 13, 2012 at 11:34 AM, Thomas Bächler thomas@archlinux.org wrote:
With systemd being the default, we have no simple network management besides dhcp by default. Should we add netcfg to the base group so it is installed by default?
I noticed this is now carried out in [testing]. The PKGBUILD is maintained as part of the netcfg source tree (`make pkgbuild`). Shall I push the change for the next netcfg release? The next release will be 3.0 and is due this week for [testing]. The biggest remaining problem with netcfg at this point is the completely outdated wiki. I've got a skeleton for a new wiki page, but it will take time rolling it out.
- Jouke
The PKGBUILD is necessarily maintained as part of SVN. You're free to maintain a copy in the source tree, but I really wouldn't count on using that for anything more than to create a git build directly from the tree itself (e.g. initscripts and mkinitcpio do this).
d
I don't have access to the SVN plus this setup makes it easy to fill in the right version and md5sum. Regardless, the question remains: is this change serious, or is it just trying to see how it looks?
- Jouke
Am 15.10.2012 22:19, schrieb Jouke Witteveen:
I don't have access to the SVN plus this setup makes it easy to fill in the right version and md5sum. Regardless, the question remains: is this change serious, or is it just trying to see how it looks?
netcfg will stay in the base group.
arch-projects@lists.archlinux.org