[MacPorts] #48184: [NEW] kf5-attica
MacPorts
noreply at macports.org
Sat Jun 27 00:53:46 PDT 2015
#48184: [NEW] kf5-attica
-------------------------+----------------------
Reporter: mk@… | Owner: mk@…
Type: submission | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords: haspatch
Port: kf5-attica |
-------------------------+----------------------
Comment (by rjvbertin@…):
You're probably better acquainted with building KF5 most all on here, but
be careful that you don't end up duplicating lots of stuff.
IF KF5 has a single versioning scheme for all or at least a good part of
its frameworks that gets built through the kdesrc-or-what's-it-called
script, I'd strongly advise to use your KDE/CI experience to coerce that
script into a portfile.
There *must* be a KF5 "subset" (a collection of frameworks) that one will
have to install anyway in order to run a productivity application
(KDevelop, KDE PIM, digiKam, ...).
Introducting countless individual ports one by one that each provide a
single framework that is of no use in itself seems like an approach that
won't attract a lot of interest. A single port that builds an ensemble
that makes sense (= that you can do something with) seems a lot more
interesting as a target to collaborate on.
That approach should also allow you to move stuff (name, description,
version, probably a bunch of the configure args) out of the kf5 portgroup
because they relate only to building KF5 and not building dependents (say,
digiKam).
Alternatively, you'd probably want to rename the portgroup to something
that makes it clear it's an internal include file, not something to be
used by any other port that provides an application that depends on KF5.
--
Ticket URL: <https://trac.macports.org/ticket/48184#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list