[MacPorts] #51344: seqan @2.1.1_0 Fixes installation of missing files
#51344: seqan @2.1.1_0 Fixes installation of missing files -------------------------+-------------------------------- Reporter: rene.rahn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: seqan | Port: seqan -------------------------+-------------------------------- Adds two more commands in destroot script to: * install `FindSeqan.cmake` into `${destroot}${prefix}/share/$cmake`, whereby `$cmake` is determined by a pre-destroot script, and * install `seqan-2.pc` into `${destroot}${prefix}/share/pkgconfig`. These files are needed, so other projects can build against the SeqAn library more easily. -- Ticket URL: <https://trac.macports.org/ticket/51344> MacPorts <https://www.macports.org/> Ports system for OS X
#51344: seqan @2.1.1_0 Fixes installation of missing files --------------------------+-------------------------------- Reporter: rene.rahn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: seqan Port: seqan | --------------------------+-------------------------------- Changes (by mf2k@…): * priority: High => Normal Comment: The Priority field is for use by Macports team members only. -- Ticket URL: <https://trac.macports.org/ticket/51344#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#51344: seqan @2.1.1_0 Fixes installation of missing files --------------------------+--------------------------------- Reporter: rene.rahn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | --------------------------+--------------------------------- Changes (by ryandesign@…): * keywords: seqan => haspatch maintainer Comment: If this changes the files the port installs, the port's revision must be increased. -- Ticket URL: <https://trac.macports.org/ticket/51344#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#51344: seqan @2.1.1_0 Fixes installation of missing files --------------------------+--------------------------------- Reporter: rene.rahn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | --------------------------+--------------------------------- Comment (by ryandesign@…): It looks like the code in the pre-destroot block will cause the port to install files into different places, depending on what directories exist on the user's system. We don't want that; we want port installs to be [ReproducibleBuilds reproducible] and the same on every system. On my system I see both a share/cmake and a share/cmake-3.5 directory? Do we know why this is? -- Ticket URL: <https://trac.macports.org/ticket/51344#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#51344: seqan @2.1.1_0 Fixes installation of missing files --------------------------+--------------------------------- Reporter: rene.rahn@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: haspatch maintainer Port: seqan | --------------------------+--------------------------------- Comment (by rene.rahn@…): Replying to [comment:3 ryandesign@…]:
It looks like the code in the pre-destroot block will cause the port to install files into different places, depending on what directories exist on the user's system. We don't want that; we want port installs to be [ReproducibleBuilds reproducible] and the same on every system.
On my system I see both a share/cmake and a share/cmake-3.5 directory? Do we know why this is? [[BR]] I am also not so happy with this solution, but needed a fallback option, if cmake is not installed yet, since we don't require it for our library installation. Another approach would be to always install into `${prefix}/share/cmake` (which seems to be the default location on linux systems) and notify the user to set a symlink to this module from within the installed cmake module path? I just realised, that if cmake is installed via dmg installer the default modules location would be under package contents in the applications folder, wouldn't it? So this would solve the problem of variable install locations and different cmake installation directories.
But I am not so sure, what here the policies are with user messages during the installation phase?! -- Ticket URL: <https://trac.macports.org/ticket/51344#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts