Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
In a python 3.x environment, the unversioned symlink to sphinx-build points
to the python 3.x version which will cause the build to fail. This port
can only use python 2.7, so we need to specify the version of sphinx-build.
This was supposedly fixed in r467840 and the PR was closed, but I was
informed by fluffy via private mail that it was still broken.
PR: 227260
Submitted by: fluffy
Approved by: portmgr (blanket - trivial build fix)
There is something strange going on here. Maybe with the way Github makes
these archives?
In r463680 we had for the same file/same git hash:
SHA256 (ceph-ceph-erasure-code-corpus-2d7d78b_GH0.tar.gz) = 466f7185015df8d13f8b2b9a17ee30ab419bcd667284ce2b6d32a1128c4640f1
SIZE (ceph-ceph-erasure-code-corpus-2d7d78b_GH0.tar.gz) = 3634266
Then in r474922 it was changed to:
SHA256 (ceph-ceph-erasure-code-corpus-2d7d78b_GH0.tar.gz) = 8ab8f36f3e0a720c882b8bb4abb3f2e26bd6b025cc263119207f7d2eb3b1e490
SIZE (ceph-ceph-erasure-code-corpus-2d7d78b_GH0.tar.gz) = 3685656
When I was working on this port the 8ab8f36 checksum failed, but the 466f718
checksum worked, so I changed back in r477944. Now it seems the 8ab8f36
checksum is working and 466f718 is not.
I have both files. Both are identical when extracted. The only difference
appears to be the compression ratio. As of right now I can only download
the 8ab8f36 file.
Reported by: fluffy
- Fix distinfo (checksum and size were corrupted in last update)
- Remove security/crytopp dependency that the port does not use
- Fix typo in IGNORE message
- Move pkgconf dependency to USES
- Depend on python ports correctly
- Remove CMAKE_BUILD_TYPE - it already is set to "Release" by the framework
- Bump PORTREVISION for dependency changes
PR: 230665
Submitted by: Willem Jan Withagen <wjw@digiware.nl> (maintainer)
Unsuffixed binaries are only installed for default python version.
$ DEFAULT_VERSIONS=python=3.6 make
[...]
===> ceph-12.2.4_1 depends on executable: sphinx-build - not found
===> ceph-12.2.4_1 depends on executable: virtualenv - not found
PR: 227260
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
Ceph is a distributed object store and file system designed to provide
excellent performance, reliability and scalability.
* Object Storage
Ceph provides seamless access to objects using native language bindings or
radosgw, a REST interface for applications written with S3 and Swift.
* Block Storage
Ceph's RADOS Block Device (RBD) provides access to block device images
that are striped and replicated across the entire storage cluster.
* File System
Ceph provides a POSIX-compliant network file system aiming for large data
storage, high performance, and maximum compatibility with legacy applications.
This FreeBSD build will build most of the tools in Ceph:
* Mon, OSD, rados, RadosGW, rbd
* init-ceph, and etc/rc.d/ceph on top of that
* ceph-disk {prepare, activate}
With these tools one can build a multi server, multi osd cluster fully
running on FreeBSD and do some testing...
WWW: http://ceph.com
PR: 221997
Submitted by: Willem Jan Withagen <wjw@digiware.nl>
