On Thu, 2024-04-18 at 00:34 +0200, Santiago Vila wrote: > > > I think you might be overestimating the importance of this.
Well I haven't said it would be super important (not at least that the dirs are created - what might be more important is, if e.g. owners are changed, like when stuff was owned by staff (pun intended ;-) ). > Regarding your idea of writing a script which "updates" all those > minor things: Feel free to do so, but I don't think it belongs > to base-files. In fact, there are a lot of things which differ > between > an upgraded system and a newly installed system, and the differences > due to more or less empty directories in /usr/local are probably > the least important of all of them. I don't think that a tool from some nobody:nogroup on github would help a lit here. At least I wouldn't trust such a thing ;-) > I often had additional recipes to achieve exactly what you > mention: that an upgraded system is as close as possible to a newly > installed system. I do basically the same, and even in the more recent stable releases, the steps needed were actually quite a lot. In general I think that it would be best that if people do upgrade, they should get a system which is a close to fresh one as reasonable possible. And such things like changed owners/permissions or not cleaned up left over dirs/files *may* actually become important at some point. Take for example the :staff thing. IIRC, that's no longer done. So people may have left over dirs still owned by :staff. Maybe in 10 years from now, staff itself has become complete obsolete, like e.g. the gnats was stopped from being created (but not removed, obviously). In 10 further years, someone might think that it's time that that UID can be reused. Which might be an issue for people who still have it because of only ever having upgraded, and which never even realised that they might need to clean up. Cheers, Chris.
