myDSL Extensions (deprecated) :: Has anyone built an msttcorefonts.dsl?
If the installation is a one-step process, you might avoid creating a dsl package by adding the install command to /opt/bootlocal.sh:
dpkg -i /path/to/msttcorefonts.deb
the problem with relying on a deb would be that a livecd user could not use the corefonts package without enabling apt.
Personally, I think an extension that simply loaded all the fonts in a given directory would be far more versatile and less likely to get anyone sued into non-existence.
...of course if someone tossed their copy of c:\$WINDIR\fonts at the script it couldn't really be helped. ;-)
Not to mention that the msttcorefonts.deb package has a postinst script that requires the user to input a directory where the font .exe files reside and then it has to go through and do the extraction/installation for each one.
My first attempt at this sort of worked but all the fonts install to /usr/share which chews up way too much space in the ramdisk. I've now managed to manually build an extension that keeps everything in /opt and just symlinks it all into the normal Debian places. Now I need to script up the creation of the extension. Unfortunately I'm currently working 14 hour days debugging custom device drivers for an embedded PowerPC Linux system so it may be a week or two before I can get back to playing with DSL.
doesn't symlinking everything into "the proper debian places" necessitate loading much of the system (/etc /usr, etc) into the ramdisk? If so, it sort of defeats the purpose of installing everything to /opt.
.dsl extensions, as I understand it, run the mkwriteable script. While this isn't a bad thing™ persay, it does up the memory load as compared to truly self-contained extensions (.tar.gz, .ci) that run entirely from /opt.
Is there a way to symlink everything into place without running mkwriteable? if so, I'd love to know about it for a few of the extensions I'm working on.
If you just need to add a font path, you can use the command "xset +fp /path/to/new/fonts"
As far as symlinks without running mkwriteable, i think it depends on what is being linked. An executable or library can be added to search paths using the PATH and LD_LIBRARY_PATH variables. I couldn't say if it's possible to do something similar with directories or hard-coded paths
Next Page...
original here.