devel/electron11 fetching behind a proxy
Hello, i try to build editors/vscode, this needs devel/electron11. Unfortunately electron cant fetch its files: [00:00:27] [1/4] Resolving packages... [00:00:27] [2/4] Fetching packages... [00:01:42] info There appears to be trouble with your network connection. Retrying... [00:03:00] info There appears to be trouble with your network connection. Retrying... [00:04:18] info There appears to be trouble with your network connection. Retrying... It tries to reach an address 0.0.12.56: 131 123.954021073 192.168.0.116 ? 0.0.12.56 TCP 74 [TCP Retransmission] 13171 ? 80 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 SACK_PERM=1 TSval=808821751 TSecr=0 132 123.954026785 192.168.0.116 ? 0.0.12.56 TCP 74 [TCP Retransmission] 57156 ? 80 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 SACK_PERM=1 TSval=725678000 TSecr=0 133 123.954032590 192.168.0.116 ? 0.0.12.56 TCP 74 [TCP Retransmission] 39187 ? 80 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 SACK_PERM=1 TSval=826552890 TSecr=0 134 123.954038148 192.168.0.116 ? 0.0.12.56 TCP 74 [TCP Retransmission] 44263 ? 80 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 WS=64 SACK_PERM=1 TSval=1959712912 TSecr=0 And my yarn error log: Trace: Error: https://registry.yarnpkg.com/fs-extra/-/fs-extra-8.1.0.tgz: tunneling socket could not be established, cause=connect ETIMEDOUT 0.0.12.56:80 at ClientRequest.onError (/usr/local/lib/node_modules/yarn/lib/cli.js:152220:17) at Object.onceWrapper (events.js:421:26) at ClientRequest.emit (events.js:314:20) at Socket.socketErrorListener (_http_client.js:427:9) at Socket.emit (events.js:314:20) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21) Do i need to set the right proxy in npm? if yes how i am going to do this? Fetching via our proxy works for other ports, this is defined in my poudriere.conf: # If you are using a proxy define it here: export HTTP_PROXY=squid:3128 This is my env in the jail after running testport: Edit /etc/motd to change this login announcement. root@j12p64-default-desktop:~ # env USER=root LOGNAME=root HOME=/root SHELL=/bin/csh OSVERSION=1202505 UNAME_v=FreeBSD 12.2-STABLE 1202505 UNAME_r=12.2-STABLE BLOCKSIZE=K MAIL=/var/mail/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin TERM=xterm-256color HOSTTYPE=FreeBSD VENDOR=amd OSTYPE=FreeBSD MACHTYPE=x86_64 SHLVL=1 PWD=/root GROUP=wheel HOST=j12p64-default-desktop EDITOR=vi PAGER=less Maybe anybody got a hint where to look at. Kind regards, Henrik Rosenke ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
poudriere merging multiple ports trees
Greetings,
this patch had a few errors that are fixed with this patch, checking for
NOT_MOVED and dont produce an error if its not there and also dont
delete packages that are in NOT_MOVED to build them again.
This Patch targets poudriere-devel 3.3.99.20200326_2
--- common.sh.1st 2021-01-27 15:44:15.0 +0100
+++ common.sh 2021-02-04 20:30:42.061211000 +0100
@@ -5040,7 +5040,10 @@
fi
if shash_get origin-moved "${origin}" new_origin; then
- if [ "${new_origin%% *}" = "EXPIRED" ]; then
+ # check also against NOT_MOVED from overlays so we dont
delete this package if its wanted
+ if [ -f ${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS#
}/NOT_MOVED ] && (grep -q "${origin}"
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED); then
+ msg_debug "${origin} is found in
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED so dont delete this
package."
+ elif [ "${new_origin%% *}" = "EXPIRED" ]; then
msg "Deleting ${pkg##*/}:
${COLOR_PORT}${origin}${COLOR_RESET} ${new_origin#EXPIRED }"
else
msg "Deleting ${pkg##*/}:
${COLOR_PORT}${origin}${COLOR_RESET} moved to
${COLOR_PORT}${new_origin}${COLOR_RESET}"
@@ -6815,8 +6818,11 @@
continue
fi
origin_listed="${origin}"
- if shash_get origin-moved "${origin}" new_origin; then
- if [ "${new_origin%% *}" = "EXPIRED" ]; then
+ # check against the overlay list, skip port if its in there
+ if [ -f ${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS#
}/NOT_MOVED ] && (grep -q "${origin}"
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED); then
+ msg_debug "${origin} found in
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED, skipped checking
MOVED File of master portstree"
+ elif shash_get origin-moved "${origin}" new_origin; then
+ if [ "${new_origin%% *}" = "EXPIRED" ] ; then
msg_error "MOVED: ${origin} ${new_origin}"
set_dep_fatal_error
continue
@@ -7085,6 +7091,10 @@
fi
[ -f ${MASTERMNT}${PORTSDIR}/MOVED ] || return 0
msg "Loading MOVED for ${MASTERMNT}${PORTSDIR}"
+ # Respect overlays, ${OVERLAYS} has a leading whitepace
+ if [ -f ${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED ]; then
+ msg "Loading NOT_MOVED from overlaydir:
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }"
+ fi
bset status "loading_moved:"
awk -f ${AWKPREFIX}/parse_MOVED.awk \
${MASTERMNT}${PORTSDIR}/MOVED | \
Kind regards,
Henrik Rosenke
Am 29.01.21 um 17:38 schrieb Henrik Rosenke:
Greetings,
i created a simple patch for this, this may not be the best solution
but my tests seems to be successful to get the desired result:
Without NOT_MOVED:
=>> Debug: Reading /usr/local/etc/poudriere.conf
[00:00:00] Creating the reference jail... done
[00:00:02] Mounting system devices for j12p64-default-server
[00:00:02] Mounting ports/packages/distfiles
[00:00:02] Using packages from previously failed build:
/home/poudriere/data/packages/j12p64-default-server/.building
[00:00:02] Mounting ccache from: /home/poudriere/ccache
[00:00:02] Mounting packages from:
/home/poudriere/data/packages/j12p64-default-server
[00:00:02] Copying /var/db/ports from:
/usr/local/etc/poudriere.d/j12p64-options
[00:00:02] Appending to make.conf: /usr/local/etc/poudriere.d/make.conf
[00:00:02] Appending to make.conf:
/usr/local/etc/poudriere.d/server-make.conf
[00:00:02] Appending to make.conf:
/usr/local/etc/poudriere.d/default-make.conf
[00:00:02] Appending to make.conf:
/usr/local/etc/poudriere.d/j12p64-make.conf
[00:00:02] Appending to make.conf:
/usr/local/etc/poudriere.d/default-server-make.conf
[00:00:02] Warning: Blacklisting (from
/usr/local/etc/poudriere.d/j12p64-blacklist): comms/chan_capi
[00:00:02] Warning: Blacklisting (from
/usr/local/etc/poudriere.d/j12p64-blacklist): comms/isdn4bsd-kmod
[00:00:02] Warning: Blacklisting (from
/usr/local/etc/poudriere.d/j12p64-blacklist): comms/isdn4bsd-utils
[00:00:02] Warning: Blacklisting (from
/usr/local/etc/poudriere.d/j12p64-blacklist): sysutils/env4801
[00:00:02] Warning: Blacklisting (from
/usr/local/etc/poudriere.d/j12p64-blacklist): security/ipsec-tools
/etc/resolv.conf ->
/home/poudriere/data/.m/j12p64-default-server/ref/etc/resolv.conf
[00:00:02] Starting jail j12p64-default-server
[00:00:02] Logs:
/home/poudriere/data/logs/bulk/j12p64-default-server/2021-01-29_11h14m59s
[00:00:02] WWW:
http
Re: poudriere merging multiple ports trees
queueing sysutils/sge62 into gatherqueue (rdep=listed)
[00:00:03] Debug: Processing gatherqueue
[00:00:03] Warning: (sysutils/sge62): Debug: gather_port_vars_port
(sysutils/sge62): LOOKUP
[00:00:03] Warning: (sysutils/sge62): Debug: deps_fetch_vars: discovered
sysutils/sge62 is sge-6.2.2.1_6
[00:00:03] Warning: (sysutils/sge62): Debug: WILL BUILD sysutils/sge62
Patch leading to this:
--- /usr/local/share/poudriere/common.sh.1st 2021-01-27
15:44:15.0 +0100
+++ /usr/local/share/poudriere/common.sh 2021-01-29
17:27:14.810441000 +0100
@@ -6815,8 +6815,11 @@
continue
fi
origin_listed="${origin}"
- if shash_get origin-moved "${origin}" new_origin; then
- if [ "${new_origin%% *}" = "EXPIRED" ]; then
+ # check against the overlay list, skip port if its in there
+ if (grep -q "${origin}"
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED); then
+ msg_debug "${origin} found in
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED, skipped checking
MOVED File of master portstree"
+ elif shash_get origin-moved "${origin}" new_origin; then
+ if [ "${new_origin%% *}" = "EXPIRED" ] ; then
msg_error "MOVED: ${origin} ${new_origin}"
set_dep_fatal_error
continue
@@ -7085,6 +7088,10 @@
fi
[ -f ${MASTERMNT}${PORTSDIR}/MOVED ] || return 0
msg "Loading MOVED for ${MASTERMNT}${PORTSDIR}"
+ # Respect overlays, ${OVERLAYS} has a leading whitepace
+ if [ -f ${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }/NOT_MOVED ]; then
+ msg "Loading NOT_MOVED from overlaydir:
${MASTERMNT}${OVERLAYSDIR}/${OVERLAYS# }"
+ fi
bset status "loading_moved:"
awk -f ${AWKPREFIX}/parse_MOVED.awk \
${MASTERMNT}${PORTSDIR}/MOVED | \
Maybe someone else could test this, seems to work for me.
Kind regards,
Henrik Rosenke
Am 28.01.21 um 21:56 schrieb Henrik Rosenke:
Am 28.01.21 um 21:14 schrieb Miroslav Lachman:
On 28/01/2021 17:47, Henrik Rosenke wrote:
I tried this with a patched MOVED file, copied from the master
portstree, deleted the entry and tried to build but this File seems
to be ignored. I dont really understand where the MOVED file is
handled, it seems to be bsd.port.subdir.mk but i am not sure.
MOVED is handled by bsd.port.subdir.mk but overlays do not account
with it. Overlays are handled on more places
i thought this too but it seems poudriere is canceled before this, i
even tried to move the bsd.port.subdir.mk and commented out the
function load_moved in the common.sh of poudriere and can start a
build. Correct me if iam wrong but it seems that the common.sh from
poudriere needs to be patched to handle this rather than the Mk files
itself. I added set -x in the common.sh to get a better understanding
what is happening and it seems that shash_set sucks in the MOVED file
and this is checked later against the ports we want to build:
+ shash_set origin-moved sysutils/sge62 'EXPIRED 2013-06-05 Has
expired: Ancient and unsupported release'
later:
+ originspec_decode sysutils/sge62 origin '' flavor
+ local -
+ set +x -f
+ [ -n '' ]
+ origin_listed=sysutils/sge62
+ shash_get origin-moved sysutils/sge62 new_origin
+ local -
+ set +x
+ [ EXPIRED '=' EXPIRED ]
+ msg_error 'MOVED: sysutils/sge62 EXPIRED 2013-06-05 Has expired:
Ancient and unsupported release'
+ local -
+ set +x
[00:00:07] Error: MOVED: sysutils/sge62 EXPIRED 2013-06-05 Has
expired: Ancient and unsupported release
Kind regards,
Henrik Rosenke
Scripts/do-depends.sh
Scripts/depends-list.sh
Next is bsd.port.mk:
.if defined(USE_LOCAL_MK)
.include "${PORTSDIR}/Mk/bsd.local.mk"
.endif
.for odir in ${OVERLAYS}
.sinclude "${odir}/Mk/bsd.overlay.mk"
.endfor
But there is no bsd.overlay.mk and I don't know what should be in it
(file in the overlay ports tree)
The AWK code in bsd.port.subdir.mk can be changed to use MOVED from
overlay if it exists insead of the default one.
I think the best way to handle this would be a NOT_MOVED file in the
overlay portstree with the ports to ignore from the MOVED file with
entries like "sysutils/sge62".
This can be possible too. NOT_MOVED can be used as additional INDEXFILE
Or maybe start with PORTSEARCH_MOVED=0 (not tried yet)
Kind regards
Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere merging multiple ports trees
Am 28.01.21 um 21:14 schrieb Miroslav Lachman:
On 28/01/2021 17:47, Henrik Rosenke wrote:
I tried this with a patched MOVED file, copied from the master
portstree, deleted the entry and tried to build but this File seems
to be ignored. I dont really understand where the MOVED file is
handled, it seems to be bsd.port.subdir.mk but i am not sure.
MOVED is handled by bsd.port.subdir.mk but overlays do not account
with it. Overlays are handled on more places
i thought this too but it seems poudriere is canceled before this, i
even tried to move the bsd.port.subdir.mk and commented out the function
load_moved in the common.sh of poudriere and can start a build. Correct
me if iam wrong but it seems that the common.sh from poudriere needs to
be patched to handle this rather than the Mk files itself. I added set
-x in the common.sh to get a better understanding what is happening and
it seems that shash_set sucks in the MOVED file and this is checked
later against the ports we want to build:
+ shash_set origin-moved sysutils/sge62 'EXPIRED 2013-06-05 Has expired:
Ancient and unsupported release'
later:
+ originspec_decode sysutils/sge62 origin '' flavor
+ local -
+ set +x -f
+ [ -n '' ]
+ origin_listed=sysutils/sge62
+ shash_get origin-moved sysutils/sge62 new_origin
+ local -
+ set +x
+ [ EXPIRED '=' EXPIRED ]
+ msg_error 'MOVED: sysutils/sge62 EXPIRED 2013-06-05 Has expired:
Ancient and unsupported release'
+ local -
+ set +x
[00:00:07] Error: MOVED: sysutils/sge62 EXPIRED 2013-06-05 Has expired:
Ancient and unsupported release
Kind regards,
Henrik Rosenke
Scripts/do-depends.sh
Scripts/depends-list.sh
Next is bsd.port.mk:
.if defined(USE_LOCAL_MK)
.include "${PORTSDIR}/Mk/bsd.local.mk"
.endif
.for odir in ${OVERLAYS}
.sinclude "${odir}/Mk/bsd.overlay.mk"
.endfor
But there is no bsd.overlay.mk and I don't know what should be in it
(file in the overlay ports tree)
The AWK code in bsd.port.subdir.mk can be changed to use MOVED from
overlay if it exists insead of the default one.
I think the best way to handle this would be a NOT_MOVED file in the
overlay portstree with the ports to ignore from the MOVED file with
entries like "sysutils/sge62".
This can be possible too. NOT_MOVED can be used as additional INDEXFILE
Or maybe start with PORTSEARCH_MOVED=0 (not tried yet)
Kind regards
Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere merging multiple ports trees
I tried this with a patched MOVED file, copied from the master portstree, deleted the entry and tried to build but this File seems to be ignored. I dont really understand where the MOVED file is handled, it seems to be bsd.port.subdir.mk but i am not sure. I think the best way to handle this would be a NOT_MOVED file in the overlay portstree with the ports to ignore from the MOVED file with entries like "sysutils/sge62". Kind regards, Henrik Rosenke Am 28.01.21 um 11:21 schrieb Miroslav Lachman: On 28/01/2021 10:55, Henrik Rosenke wrote: Greetings, UIDs and GIDs are also not resprected, i could solve this via this patch: I didn't tried it but what if you have patched Mk/bsd.port.mk and MOVED in overlay tree? Does it work or not? Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere merging multiple ports trees
Greetings,
UIDs and GIDs are also not resprected, i could solve this via this patch:
Index: Mk/bsd.port.mk
===
--- Mk/bsd.port.mk (Revision 563120)
+++ Mk/bsd.port.mk (Arbeitskopie)
@@ -1274,8 +1274,17 @@
# where 'make config' records user configuration options
PORT_DBDIR?= /var/db/ports
+# add support for overlaying UIDs and GIDs, dont include them if they
dont exist
+.if exists(${OVERLAYS}/UIDs)
+UID_FILES?= ${OVERLAYS}/UIDs ${PORTSDIR}/UIDs
+.else
UID_FILES?= ${PORTSDIR}/UIDs
+.endif
+.if exists(${OVERLAYS}/GIDs)
+GID_FILES?= ${OVERLAYS}/GIDs ${PORTSDIR}/GIDs
+.else
GID_FILES?= ${PORTSDIR}/GIDs
+.endif
UID_OFFSET?= 0
GID_OFFSET?= 0
Maybe this could be implented upstream to support overlaying GIDs and UIDs
Kind regards,
Henrik Rosenke
Am 27.01.21 um 17:57 schrieb Henrik Rosenke:
Greetings,
i just added the overlay to my portstree, works good and great
addition. I wonder how you handle moved ports with this? As example we
are using a adapted Version of sysutils/sge62 with own patches but i
need to remove this Line in MOVED on the Original portstree to allow
building it. Is there a way to handle such exceptions or do i need to
rename it? Is there any Documentation about this?
Kind regards,
Henrik Rosenke
Am 25.01.21 um 16:28 schrieb Baptiste Daroussin:
On Mon, Jan 25, 2021 at 04:25:09PM +0100, Miroslav Lachman wrote:
On 25/01/2021 15:10, Baptiste Daroussin wrote:
On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via
freebsd-ports wrote:
On 24/01/21 20:35, Russell L. Carter wrote:
Greetings,
I am completely ignorant here and am looking for up to
date advice on how to get poudriere to build and make
available package sets from multiple ports trees. I
see there is a port "portshaker" that seems to do much
of what I want.
[...]
BTW I noticed poudriere performs shallow clones for git repos, so
it should
not use up a lot of disk space.
Why not using directly overlays, it will simplify everything ;)
I don't know if you read me reply or not - I am using poudriere with
ports
overlay but have a problem with it. Poudriere options does not take
overlay
in to account so ports options cannot be configured for overlayed ports
which do not exist in the base three.
Is there a way to fix it / should I file a PR for it?
Kind regards
Miroslav Lachman
Yes I read it and for sure poudriere option not supporting overlays is a
limitation, and yes a PR would help to not forget about implementing it.
That said most people aren't using poudriere option and prefer to
define option
directly via make.conf for them overlay is fully suited, and avoid
the risk or
dangerous merging of trees may it be via portshaker, or git mechanism.
there are room of improvements for overlays but it should work in
most cases
Best regards,
Bapt
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: poudriere merging multiple ports trees
Greetings, i just added the overlay to my portstree, works good and great addition. I wonder how you handle moved ports with this? As example we are using a adapted Version of sysutils/sge62 with own patches but i need to remove this Line in MOVED on the Original portstree to allow building it. Is there a way to handle such exceptions or do i need to rename it? Is there any Documentation about this? Kind regards, Henrik Rosenke Am 25.01.21 um 16:28 schrieb Baptiste Daroussin: On Mon, Jan 25, 2021 at 04:25:09PM +0100, Miroslav Lachman wrote: On 25/01/2021 15:10, Baptiste Daroussin wrote: On Sun, Jan 24, 2021 at 10:23:45PM +0100, Guido Falsi via freebsd-ports wrote: On 24/01/21 20:35, Russell L. Carter wrote: Greetings, I am completely ignorant here and am looking for up to date advice on how to get poudriere to build and make available package sets from multiple ports trees. I see there is a port "portshaker" that seems to do much of what I want. [...] BTW I noticed poudriere performs shallow clones for git repos, so it should not use up a lot of disk space. Why not using directly overlays, it will simplify everything ;) I don't know if you read me reply or not - I am using poudriere with ports overlay but have a problem with it. Poudriere options does not take overlay in to account so ports options cannot be configured for overlayed ports which do not exist in the base three. Is there a way to fix it / should I file a PR for it? Kind regards Miroslav Lachman Yes I read it and for sure poudriere option not supporting overlays is a limitation, and yes a PR would help to not forget about implementing it. That said most people aren't using poudriere option and prefer to define option directly via make.conf for them overlay is fully suited, and avoid the risk or dangerous merging of trees may it be via portshaker, or git mechanism. there are room of improvements for overlays but it should work in most cases Best regards, Bapt ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: OpenSource app Simple Diary
Am 03.01.21 um 11:27 schrieb Jan Beich: Henrik Rosenke writes: Hello, Am 03.01.21 um 11:12 schrieb Chris: On 2021-01-03 01:57, Matthias Apitz wrote: Hello, In the forum about the mobile Purism L5 someone announced some app to write a diary: https://forums.puri.sm/t/app-simple-diary/11508 https://github.com/johan-bjareholt/simple-diary-gtk I have below its README file. Its dependencies are: - GTK+3 x11-toolkits/gtk30/ ? - webkit2gtk-4.0 www/webkit2-gtk3/ - md4c and md4c-html - Not quite sure what these might translate to. See https://repology.org/project/md4c/information md4c could be contained in qt: https://doc.qt.io/qt-5/qtgui-attribution-md4c.html but i dont know if our qt is build with this or if another qt port with this feature exists. From x11-toolkits/qt5-gui build log: Checking for libmd4c... no [...] Qt Gui: Text formats: MarkdownReader ... yes Using system libmd4c ... no http://beefy6.nyi.freebsd.org/data/121amd64-default/559329/logs/qt5-gui-5.15.2_2.log I created a new port for md4c and md2html with the sources from https://github.com/mity/md4c Maybe could a Commiter take a look on https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252383 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: OpenSource app Simple Diary
Hello, Am 03.01.21 um 11:12 schrieb Chris: On 2021-01-03 01:57, Matthias Apitz wrote: Hello, In the forum about the mobile Purism L5 someone announced some app to write a diary: https://forums.puri.sm/t/app-simple-diary/11508 https://github.com/johan-bjareholt/simple-diary-gtk I have below its README file. Its dependencies are: - GTK+3 x11-toolkits/gtk30/ ? - webkit2gtk-4.0 www/webkit2-gtk3/ - md4c and md4c-html - Not quite sure what these might translate to. md4c could be contained in qt: https://doc.qt.io/qt-5/qtgui-attribution-md4c.html but i dont know if our qt is build with this or if another qt port with this feature exists. --Chris Do we have them in our ports collection in head? I couldn't see them, at least not with the above names exactly. Thanks matthias Simple Diary Simple and lightweight diary app. Many features are still missing as this is a work in progress. ### Features - Saves entries in markdown - Adding images to your entries - Works for small form factor devices - Flatpak support ### Dependencies - GTK+3 - webkit2gtk-4.0 - md4c and md4c-html ### Building # Meson First install dependencies listed above Secondly run the following: meson build && ninja -C build Executable will be built at build/src/simple-diary # Flatpak Build the org.johanbjare.SimpleDiary.yml manifest as with any other flatpak manifest with flatpak-builder ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
poudriere: build pkg with tests
Hello, by testing with 2 repositories pkg does not always install the right packages. After searching i found this: https://github.com/freebsd/pkg/issues/1186 How can i build pkg with tests in poudriere to run these tests? This seems not to be documented anywhere Greetings, Henrik Rosenke ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
