* frantisek holop <[EMAIL PROTECTED]> [081015 13:14]:
> here is what i want to do:
>
> i am using the ports framework to automate
> a process which overwrites/deletes some existing
> files of installed packages.
Doesn't this compromise the pkg system right from the start? The point
of packages is to manage the orderly addition and removal of software
while accounting for dependencies.
>
> overwriting is not a problem and deleting these
> mutilated packages with pkg_delete -q is ok
> too. but how can i delete some existing files
> before the package is actually installed?
>
> the very practical example of this is updating
> the lm fonts in the old tetex packages.
>
Shouldn't the old package take care of itself? That is, shouldn't it
remove it's own files?
> filenames have changed, so the best is to delete
> certain directories and i tried with exec in PLIST
>
> @exec rm -rf
> /usr/local/share/texmf-dist/fonts/{afm,opentype,tfm,type1}/public/lm
> @exec rm -rf /usr/local/share/texmf-dist/fonts/{enc,map}/dvips/lm
>
> but this fails miserably because conflicts are detected
> much sooner.... Marc? :]
>
> -f
> --
> the current death rate? one per person, of course.
>
If your package updates an existing package, the package framework
should take care of you. Perhaps your making this harder than it needs
to be or I'm missing something.
Jim
