Summary: | sys-apps/portage-2.1.10.49 etc-update finds rc.conf twice | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sergey S. Starikoff <Ikonta> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | trivial | ||
Priority: | Normal | ||
Version: | 2.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey S. Starikoff
2012-05-25 19:16:43 UTC
What does the etc-update output look like? (In reply to comment #0) > CONFIG_PROTECT="/etc /etc/conf.d/clock /etc/rc.conf > /usr/share/gnupg/qualified.txt /var/bind" Having both /etc and /etc/rc.conf in CONFIG_PROTECT is what triggers this. (In reply to comment #1) > What does the etc-update output look like? Like standard one. Quotting by memory: 1) rc.conf ... (some other config files to be updated) 41) rc.conf Really the last rc.conf item is not processed. (In reply to comment #2) > (In reply to comment #0) > > CONFIG_PROTECT="/etc /etc/conf.d/clock /etc/rc.conf > > /usr/share/gnupg/qualified.txt /var/bind" > > Having both /etc and /etc/rc.conf in CONFIG_PROTECT is what triggers this. Maybe we should just consider this "user error" and close a WONTFIX? (In reply to comment #4) > Maybe we should just consider this "user error" and close a WONTFIX? Looking from side of portage operability it seems not to be issue at all. But I think that finding (and putting into result list) one file needs update two times... to my mind is not right. Even if it is processed only one time. Up to you. (In reply to comment #5) > Looking from side of portage operability it seems not to be issue at all. Why do you have both /etc and /etc/rc.conf in CONFIG_PROTECT though? Isn't it redundant? > But I think that finding (and putting into result list) one file needs > update two times... to my mind is not right. Even if it is processed only > one time. Unless there's some good reason to list both /etc and /etc/rc.conf in CONFIG_PROTECT, then you should remove /etc/rc.conf from CONFIG_PROTECT. Can you give a reason? |