Re: pre-build packages for Lion
>> What are the intervals that pre-build packages for Lion are >> generated? For example, `libpaper` is already available, but >> `ghostscript` is not > > There will not be any prebuilt archives available for ghostscript > for any macOS version where one of its dependents, e.g. libpaper, is > using legacy-support: D'oh, thanks. Werner
Re: Re: pre-build packages for Lion
On 12/10/23 at 2:07 AM, Christopher A. Chavez via macports-users wrote: > where one of its dependents I meant to say “one of its dependencies”.
Re: pre-build packages for Lion
On 12/10/23 at 12:47 AM, Werner LEMBERG wrote: > What are the intervals that pre-build packages for Lion are generated? > For example, `libpaper` is already available, but `ghostscript` is not There will not be any prebuilt archives available for ghostscript for any macOS version where one of its dependents, e.g. libpaper, is using legacy-support: > "ghostscript" is not distributable because its license "agpl" conflicts with > license "APSL-2" of dependency "legacy-support" https://build.macports.org/builders/ports-10.7_x86_64-builder/builds/166656/steps/gather-archives/logs/stdio
pre-build packages for Lion
What are the intervals that pre-build packages for Lion are generated? For example, `libpaper` is already available, but `ghostscript` is not, and neither is 'texlive-bin'... And while we are at it, 'ports.macports.org' reports that 'lilypond' can't be build on Lion due to ``` Dependency 'poppler' with variants '+boost' has previously failed and is required. ``` (why is `+boost` needed?) However, looking into the 'poppler' page on 'ports.macports.org' it seems that the Lion build is healthy – and the variant '+boost' has been just built from source on my computer without a problem... Werner
