Package Details: scotch 7.0.6-1

Git Clone URL: https://aur.archlinux.org/scotch.git (read-only, click to copy)
Package Base: scotch
Description: Software package and libraries for graph, mesh and hypergraph partitioning, static mapping, and sparse matrix block ordering
Upstream URL: https://gitlab.inria.fr/scotch/scotch
Licenses: CeCILL-C
Conflicts: ptscotch-openmpi, scotch_esmumps, scotch_esmumps5
Provides: ptscotch, ptscotch-openmpi, scotch_esmumps, scotch_ptesmumps
Submitter: None
Maintainer: ioquatix (MartinDiehl)
Last Packager: MartinDiehl
Votes: 41
Popularity: 0.78
First Submitted: 2006-11-07 17:51 (UTC)
Last Updated: 2024-12-06 16:25 (UTC)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 Next › Last »

eolianoe commented on 2015-02-19 08:23 (UTC)

@eleftg: after some tests it seems that you can't use scotch if you do not have bzip2 installed, so it should not be an optional dependency.

eleftg commented on 2015-02-19 07:29 (UTC)

Updated. -- Removed scotch_esmumps5 from provides -- Removed -DSCOTCH_PTHREAD right before building the MPI versions

eolianoe commented on 2015-02-16 11:49 (UTC)

@eleftg: * yes, you should keep ptscotch-openmpi until the depends arrays of the other package are updateed, * according to http://mumps.enseeiht.fr/index.php?page=faq#20, mumps could depend on scotch v6.0.1, and the mumps package should be update to depend to this new version of scotch, * you should ask for merge request rather than deletion in order to keep comments and votes, * for bzip2 I do not have any idea on that, maybe a more experienced user ofo scotch could answer.

eleftg commented on 2015-02-16 09:57 (UTC)

@ eolianoe: Thank you very much. I (almost) entirely adopted your PKGBUILD :-) "Almost" because: -- indeed, ptscotch-mpich2 is not provided. But... -- ptscotch-openmpi is provided (since it's ptscotch built with openmpi :-) ). And if i remove it from provides=() i'm forced to uninstall openfoam. -- scotch_esmumps5 is indeed NOT provided but if i remove it, i'm forced to uninstall mumps. -- both mumps and openfoam build perfectly fine with this new version of scotch. So it can be considered as a drop-in replacement for the other *scotch* versions. -- Meanwhile I filed requests of deletion for all other scotch packages as advised in https://lists.archlinux.org/pipermail/aur-general/2015-February/030301.html -- also enabled an optional dependency: bzip2 (which unfortunately will also constitute a make dependency for scotch and any project depending on it, however i tried both openfoam and mumps by adding -lbz2 and they built fine). I would appreciate your feedback on the above issues.

myles commented on 2015-02-15 21:03 (UTC)

I've orphaned https://aur.archlinux.org/packages/scotch_esmumps in case anyone here is interested in maintaining it

eolianoe commented on 2015-02-15 19:16 (UTC)

@eleftg: you should not provide ptscotch-mpich2, ptscotch-openmpi, and scotch_esmumps5 as there are different "projects" the first are built with different MPI and the last is a legacy version, but they should stay in the conflicts array. You should rather provide scotch, ptscotch, and scotch-esmumps as this is that your package really provides. Here is a proposal for an update PKGBUILD (which use 'make install'): http://pastebin.com/hBPqEVJ8

eleftg commented on 2015-02-14 08:05 (UTC)

Well... yes, sure. Why not?

mickele commented on 2015-01-29 08:17 (UTC)

I can rename gpart to something like gpart-scotch. What do you think about this?

eleftg commented on 2015-01-28 22:51 (UTC)

this package conflicts with gpart (https://www.archlinux.org/packages/extra/x86_64/gpart/) The reason is an executable with identical name: /usr/bin/gpart