New: System banner - change to empty doesn't remove /etc/issue
https://bugs.busybox.net/show_bug.cgi?id=5390
Summary: System banner - change to empty doesn't remove
/etc/issue
Product: buildroot
Version: 2012.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: net147 at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
After building a root filesystem, changing the system banner to nothing and then doing make doesn't remove /etc/issue from the root filesystem.
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
[Buildroot] [Bug 5390] System banner - change to empty doesn't remove /etc/issue
https://bugs.busybox.net/show_bug.cgi?id=5390
Thomas Petazzoni <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX--- Comment #1 from Thomas Petazzoni <[email protected]> 2013-12-04 20:40:05 UTC --- This is "expected": Buildroot doesn't track the configuration changes that are
made to update the root filesystem after just a "make" invocation. For example,
if you remove a package from your configuration, and then run "make", then the
files installed by this package in the previous build are not going to be
removed from the root filesystem.
It's the same for this /etc/issue thing. If the BR2_TARGET_GENERIC_ISSUE option is empty at the first build, then no /etc/issue file gets created.
Otherwise, if you change BR2_TARGET_GENERIC_ISSUE after the first build, then the file will remain as it was before, until you do a "make clean all" cycle.
Even though fixing this would not be very difficult, I don't think we really want to do it, since we anyway don't do it for the vast majority of other Buildroot configuration options.
Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.