On Monday November 30 2015 12:21:33 Rainer Müller wrote:
> Be aware there might be a difference whether you create a file with
> low-level system calls (for example cp in Terminal) or with Finder. Only
> the latter automatically triggers Launch Services to recognize new items.
Yes, I'm aware of that.
I just checked: FontBook can be AppleScripted. I reckon MacPorts doesn't ship
with a Tcl/AppleScript bridge so one would have to use osascript?
> You are right, the same applies to application bundles. I was just
> thinking what happens if a user already has the font installed manually.
> Maybe the port could even print a warning on activate?
Given that with the current state of "base" we'd be writing a custom build
phase, sure.
I'd even go as far to say that it ought to be an error; as I suggested earlier
I don't think MacPorts should allow to replace items outside of ${prefix} or
other "owned" locations.
> Maybe they could be placed in the app bundle, but that would cause
> duplication across multiple ports...
Yes, and you'd have to identify all applications that might be using them.
> > In both cases it'd require a *lot* of hacking to get those fonts to be
> > found in a location that's not supported by the OS, hacking of a kind even
> > I don't feel comfortable proposing as a port patch.
>
> It makes sense, but needs more work and a new base release. Could you
> file a ticket in Trac for this?
About what exactly, supporting/providing fonts ports?
> Of course I was talking about inclusion in the main ports tree and
> mirroring.
Individual fonts may have clauses against redistribution/mirroring even if
they're free. Is there already a mechanism to prevent mirroring and force
downloading from the official master_sites?
R.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
