Am Freitag, den 31.08.2018, 23:06 +0300 schrieb Waleed Hamra via blfs-
support:
> Greetings guys;
> 
> What are some common post install commands I should know about?
> For instance, I know that if a package installs a .desktop file, I 
> should run "update-desktop-database" to update the cache. For some 
> programs there's gtk-update-icon-cache, though I don't really know
> when 
> I need to run that, I just run after every gtk package.
> 
> I had some problems with akonadi earlier, and after some debugging,
> I 
> noticed it outputting something about some mail mime types being 
> invalid, so I ran update-mime-database, and that solved it.
> 
> Anything else I should be aware about? I ask since everything is 
> installed using a DESTDIR method, so if make install is expected to
> fix 
> some of this stuff, it's not.
> 
> Thanks a lot for any pointers.
> 
> Waleed Hamra

You allready found the two most used tools to run. After installing
fonts, you may think about "fc-cache". 'info -d <dir>' maybe another
one.  Ken mentioned ldconfig for each package which does something with
libraries.

More generally spoken, the DESTDIR-method is pretty fine as long as you
take in account that sometimes the sequence of the instructions needs
to be changed. I assume you do DESTDIR to provide binary packages for
other machines than the building machine - which is IMHO the only
reason DESTDIR makes sense.
For instance, when building a daemon, the first instructions are to
create some user/groups (e.g. apache for httpd or postfix/postdrop for
postfix, etc). The users are most of the time not required for build
time (one exception is fcron), it is required when you do the install
of the DESTDIR-binary. So in this case, build postgres on machine A,
tar it up, unpack it on B and create the user/group on B (plus doing
some chown+chmod) and run the initdb stuff (what if a database is
allready there?). For user/groups its obvious, failures to create them
are reported mostly very quick. It becomes a bit more tricky when it
comes to special file-/directory-permissions. All that stuff needs to
be done on the target machine (B) - so at a very different time.
And watch out for configuration files which might exist on B allready.
Don't overwrite them, work changes into them.

--
Thomas

-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to