cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Import kgeotag-1.2.0

Browse Source 
Comment:
stand-alone photo geotagging program

Description:
Photos (e. g. JPEG images) contain metadata like the creation date, camera
information etc. Those are either stored in the so-called Exif header,
in an XMP sidecar file or in both. This data can also represent geographic
coordinates so that it's replicable where the images were taken.

Most cameras don't have GPS receivers, so, most can't save coordinates when
taking images. A common approach is to e. g. carry a small GPS logging device
along, which records a track all the time. Later on, the images' dates can
be compared to the GPS log's points' dates to figure out where an image
was taken.

If one knows for sure where the respective photo was taken, it's also
possible to assign coordinates to the images manually.

Maintainer: Rafael Sadowski <rsadowski@openbsd.org>

WWW: https://kgeotag.kde.org

Feedback and OK sdk@
This commit is contained in:
rsadowski 2022-01-04 06:28:02 +00:00
parent c2ae2ef255
commit e62fd9c9cf
4 changed files with 107 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
geo/kgeotag/Makefile Normal file
View File

@ -0,0 +1,51 @@
# $OpenBSD: Makefile,v 1.1.1.1 2022/01/04 06:28:02 rsadowski Exp $
COMMENT = stand-alone photo geotagging program
V = 1.2.0
DISTNAME = kgeotag-${V}
CATEGORIES = geo x11
HOMEPAGE = https://kgeotag.kde.org
MAINTAINER = Rafael Sadowski <rsadowski@openbsd.org>
# GPL and many others
PERMIT_PACKAGE = Yes
WANTLIB += ${COMPILER_LIBCXX} KF5Auth KF5AuthCore KF5Codecs KF5ConfigCore
WANTLIB += KF5ConfigGui KF5ConfigWidgets KF5CoreAddons KF5Crash
WANTLIB += KF5I18n KF5KExiv2 KF5WidgetsAddons KF5XmlGui Qt5Core
WANTLIB += Qt5DBus Qt5Gui Qt5Network Qt5Positioning Qt5PrintSupport
WANTLIB += Qt5Qml Qt5QmlModels Qt5Quick Qt5WebChannel Qt5WebEngine
WANTLIB += Qt5WebEngineCore Qt5WebEngineWidgets Qt5Widgets Qt5Xml
WANTLIB += c m marblewidget-qt5
MASTER_SITES = ${MASTER_SITE_KDE:=stable/kgeotag/${V}/}
MODULES = devel/kf5
BUILD_DEPENDS = devel/kf5/kdoctools \
devel/gettext,-tools
RUN_DEPENDS = devel/desktop-file-utils \
devel/kf5/kdoctools \
x11/gtk+3,-guic
LIB_DEPENDS = devel/kf5/kauth \
devel/kf5/kcodecs \
devel/kf5/kconfig \
devel/kf5/kconfigwidgets \
devel/kf5/kcoreaddons \
devel/kf5/kcrash \
devel/kf5/ki18n \
devel/kf5/kwidgetsaddons \
devel/kf5/kxmlgui \
x11/kde-applications/libkexiv2 \
x11/kde-applications/marble \
x11/qt5/qtdeclarative \
x11/qt5/qtlocation \
x11/qt5/qtwebchannel \
x11/qt5/qtwebengine
.include <bsd.port.mk>

2
geo/kgeotag/distinfo Normal file
View File

@ -0,0 +1,2 @@
SHA256 (kgeotag-1.2.0.tar.xz) = /5mwqLGtGop8Env+LIai1Yx+E7j4naVuqXKGvpNiQRg=
SIZE (kgeotag-1.2.0.tar.xz) = 284708

13
geo/kgeotag/pkg/DESCR Normal file
View File

@ -0,0 +1,13 @@
Photos (e. g. JPEG images) contain metadata like the creation date, camera
information etc. Those are either stored in the so-called Exif header,
in an XMP sidecar file or in both. This data can also represent geographic
coordinates so that it's replicable where the images were taken.
Most cameras don't have GPS receivers, so, most can't save coordinates when
taking images. A common approach is to e. g. carry a small GPS logging device
along, which records a track all the time. Later on, the images' dates can
be compared to the GPS log's points' dates to figure out where an image
was taken.
If one knows for sure where the respective photo was taken, it's also
possible to assign coordinates to the images manually.

41
geo/kgeotag/pkg/PLIST Normal file
View File

@ -0,0 +1,41 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2022/01/04 06:28:02 rsadowski Exp $
@bin bin/kgeotag
share/applications/org.kde.kgeotag.desktop
share/icons/hicolor/128x128/apps/kgeotag.png
share/icons/hicolor/16x16/apps/kgeotag.png
share/icons/hicolor/22x22/apps/kgeotag.png
share/icons/hicolor/32x32/apps/kgeotag.png
share/icons/hicolor/48x48/apps/kgeotag.png
share/icons/hicolor/64x64/apps/kgeotag.png
share/kgeotag/
share/kgeotag/timezones.json
share/kgeotag/timezones.png
share/kxmlgui5/
share/kxmlgui5/kgeotag/
share/kxmlgui5/kgeotag/kgeotagui.rc
share/locale/ca/LC_MESSAGES/kgeotag.mo
share/locale/ca@valencia/LC_MESSAGES/kgeotag.mo
share/locale/cs/LC_MESSAGES/kgeotag.mo
share/locale/de/LC_MESSAGES/kgeotag.mo
share/locale/en_GB/LC_MESSAGES/kgeotag.mo
share/locale/es/LC_MESSAGES/kgeotag.mo
share/locale/fi/LC_MESSAGES/kgeotag.mo
share/locale/fr/LC_MESSAGES/kgeotag.mo
share/locale/it/LC_MESSAGES/kgeotag.mo
share/locale/ko/LC_MESSAGES/kgeotag.mo
share/locale/nl/LC_MESSAGES/kgeotag.mo
share/locale/nn/LC_MESSAGES/kgeotag.mo
share/locale/pa/LC_MESSAGES/kgeotag.mo
share/locale/pl/LC_MESSAGES/kgeotag.mo
share/locale/pt/LC_MESSAGES/kgeotag.mo
share/locale/pt_BR/LC_MESSAGES/kgeotag.mo
share/locale/ru/LC_MESSAGES/kgeotag.mo
share/locale/sk/LC_MESSAGES/kgeotag.mo
share/locale/sl/LC_MESSAGES/kgeotag.mo
share/locale/sv/LC_MESSAGES/kgeotag.mo
share/locale/tr/LC_MESSAGES/kgeotag.mo
share/locale/uk/LC_MESSAGES/kgeotag.mo
share/locale/zh_CN/LC_MESSAGES/kgeotag.mo
share/metainfo/
share/metainfo/org.kde.kgeotag.appdata.xml
@tag gtk-update-icon-cache %D/share/icons/hicolor