Our approach to this kind of use case was to add download commands to the
pre-activate stage of the Portfile.
See the example below.
_
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil;
c-basic-offset: 4 -*- vim:fenc=utf-8:ft=
Dear Mojca,
My use case is far more ambitious. Thanks for the feedback though.
Kind regards.
Artur
From: Mojca Miklavec
Sent: 13 February 2019 09:38:35
To: Artur Szostak
Cc: Cyril Roelandt; MacPorts Development
Subject: Re: Universal packaging tool (for
What is the current practical reality of tools like upt? i.e. how well do they
behave on real packages. For example, if I take all the .src.rpm packages in
say the Fedora repository, and attempt to convert them to MacPorts packages,
what percentage of the converted packages will actually work ou
>>> Not quite. I'm noting that the package version isn't a reliable
>>> indication of the ABI version, and neither (sadly, see the current
>>> protobuf issues and the issues with LibreSSL) is the library dylib
>>> name. Thus I'm proposing to have an internal ABI revision number that
>>> we can use
>> So then there is a bug from what I understand, or cfitsio in MacPorts is
>> being built incorrectly. Compare file names for the newer Cfitsio:
>> /opt/local/lib/libcfitsio.6.3.44.dylib
>> /opt/local/lib/libcfitsio.6.dylib -> libcfitsio.6.3.44.dylib (symlink)
>> and the older Cfitsio:
>> /
> Portfile authors need to manually "revbump" the library's dependent ports
> when supporting libraries change significantly.
>
> It's not automatically figured out by MacPorts.
>
The Portfiles for cfitsio had two different versions. So I do not think that is
the issue.
>> Hi,
>>
>> I have a Portfile for a library (called CPL) that was linked against Cfitsio
>> from a week ago. Cfitsio was updated very recently. What I expect is that
>> during the installation of CPL, MacPorts is able to figure out that Cfitsio
>> changed and that CPL needs to be rebuilt. Howev
Hi,
I have a Portfile for a library (called CPL) that was linked against Cfitsio
from a week ago. Cfitsio was updated very recently. What I expect is that
during the installation of CPL, MacPorts is able to figure out that Cfitsio
changed and that CPL needs to be rebuilt. However, during the "S
Hi,
Does MacPorts support handling of configuration files installed by a port under
/opt/local/etc in a similar manner to RPM's "%config(noreplace)" mechanism?
i.e. can a configuration file be marked, and have MacPorts not clobber it if
the user changed it.
Kind regards.
Artur
2016 22:34
To: Artur Szostak
Cc: macports-...@lists.macosforge.org
Subject: Re: Issues with upgrading with private repositories
Hi,
On Wed, Nov 09, 2016 at 10:17:36AM +, Artur Szostak wrote:
> During my testing when developing Portfiles I have a few different
> private repositories conf
Dear MacPorts developers,
During my testing when developing Portfiles I have a few different private
repositories configured under /opt/local/etc/macports/sources.conf. I have
gotten into a situation where after a "sudo port sync" I am seeing a version
number that is not expected for my package
11 matches
Mail list logo
