On 21 May 2017 at 16:35, Ken Moffat <[email protected]> wrote: > On Sun, May 21, 2017 at 01:27:28PM +0100, Richard Melville wrote: > > A minor error but it made my script fail:- > > > > *Installed Directory:* /usr/share/icons/hicolor > > > > This package does not install that directory, but rather installs the > file > > "index.theme" in that directory. > > > > Richard > > I disagree. My logs from last week show that package creating that > directory. Which package do _you_ think created that directory ? >
Ken, that's a very good question. Unfortunately, if a package builds without problems I don't keep the logs. I build everything in a separate build directory, and then clear that directory on success. Maybe I should keep all the build logs in a separate directory, but I've seen no point -- until now, maybe. All I can say is that, on this build, I've only just installed hicolor-icon-theme and /usr/share/icons/hicolor was already in existence, created by an earlier package. Clearly, I could track this down as I have a list of all the packages I've installed, but it will take some time. The reason that I'm so certain is because when the hicolor-icons-theme build initially failed I checked /usr/share/icons and hicolor existed with a number of entries. As I've been working on this build sporadically over the last few months it was dated 18 March. Then, when the build of hicolor-icon-theme succeeded, the date of the directory changed to 21 May (today) as it was overwritten. Anyway, if I have the time I'll see if I can dig out the answer. Richard
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
