| Summary: | net-firewall/ipsec-tools-0.8.0-r4 & net-misc/strongswan-5.0.0 both install /etc/ipsec.conf | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | SpanKY <vapier> |
| Component: | [OLD] Server | Assignee: | Patrick Lauer <patrick> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | blueness, gurligebis |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
ipsec-tools build log strongswan build.log |
||
Created attachment 324900 [details]
ipsec-tools build log
Created attachment 324902 [details]
strongswan build.log
Great. Here's my 2 cents: 1) Changing the name ipsec.conf in strongswan is a pita. I requires everything from changing the internals of man pages and man page names to editing the header that hard codes "/etc/ipsec.conf" 2) Changing the name ipsec.conf in ipsec-tools is as easy as changing one line int /etc/conf.d/racoon. 3) Debian uses /etc/ipsec-tools.conf for ipsec-tools. Okay, the solution here is pretty obvious. ipsec-tools-0.8.0-r5 will use /etc/ipsec-tools.conf. Question: how to alert our users? What do you think of a news item with Display-If-Installed: <net-firewall/ipsec-tools-0.8.0-r5 (In reply to comment #3) changing ipsec-tools sounds reasonable (i don't care either way since i don't use either package) in terms of migration, you can add a pkg_preinst hook that looks to see if the user already has ipsec-tools installed and if so, automatically migrate the file. you can also check to see if they have strongswan installed and issue a warning in that case (and not do the file migration). Okay fixed in the tree with ipsec-tools-0.8.0-r5. |
Created attachment 324898 [details] emerge --info $ qfile /etc/ipsec.conf -v net-firewall/ipsec-tools-0.8.0-r4 (/etc/ipsec.conf) net-misc/strongswan-5.0.0 (/etc/ipsec.conf)