Re: Is there a way to display the block of another man page inside a man page
Hello Ingo, thanks for your time on this your comments and advice were very helpful just one follow up the :t functionality in man did not seem to work unless I had the .Tg telnet line added Thanks for the tip on the writing side... ( I must of gone to the school were I learnend why say something in 10 words when you can say the exact same thing in 100 words... Im taking the lessons learned from the telnet command and applying it else where in the man page thanks here is what I ended up with for the telnet command in nsh .Tg telnet .Ic telnet .Op Ar options .Op Ar host .Op port .Pp Open a .Xr telnet 1 session to the given TCP .Ar port on the remote server .Ar host , specified by name or IP address. If the port is not specified the IANA assigned port 23 for telnet will be used. The .Ar options are documented in the .Xr telnet 1 manual page. Thanks again Ingo Tom Smyth On Mon, 2 May 2022 at 02:36, Ingo Schwarze wrote: > > Hi Tom, > > Tom Smyth wrote on Mon, May 02, 2022 at 01:46:50AM +0100: > > > while documenting nsh and its features, > > I wanted to display the command switches of telnet command inside the > > manual page for nsh, > > Don't. > > This is not a technical problem: "how can i technically do this" > is the wrong question to ask. > > This is a problem of manual page design and content organisation. > Having a large amount of identical text in two manual pages is a > bad idea because readers will wonder whether the text is indeed > identical or whether there are subtle differences. They will likely > waste time by starting to compare the two pages to track down the > differences. > > Besides, displaying lots of content from one page in another is > bad documentation design because it detracts from the topic of > the other page. Instead, explain in the other page which content > of the first page also applies here, as precisely as possible. > > > I would like to display , the contents of the > > telnet , name synopsis and description sections from the telnet > > manpage in the nsh man page without copying the contents of the man > > page. (so that the command line switches / arguments are up to date > > for a given OpenBSD version > > > > for now i have done telnet client documentation in nsh as follows > > .Tg telnet > > Most likely, .Tg is not needed right in front of .Ic with the same > argument. Does :t telnet not work without it? > > > .Ic telnet > > .Op -a > > That should be ".Op Fl a"; the same applies below. > > > .Op -b host-alias > > .Op -l user-name > > .Ar host-name > > Just ".Ar host" is enough; it may not even be a name. > > > .Op Ar port > > .Pp > > Open a telnet client session to the remote host host-name. > > Better: > > Open a > .Xr telnet 1 > session to the remote server > .Ar host , > which can be specified by name or IP address. > > > Where host-name can be a name or IP address of the remote host. > > port is the TCP port on the remote host which you wish to connect and port > > can be within the range 0-65535. > > The > > .Ic -a > > switch will attempt an automatic login if the setup permits it. > > The > > .Ic -b host-alias > > will bind the source IP telnet client session to a specific ip address alias > > rather than the primary ip address on a given interface. > > See > > the > > > .Xr telnet 1 > > man page for a comprehensive list of telnet command options. > > Yes, that is how to do it. > Nits: s/man/manual/; s/command/command line/ > > I think i would trim this down even more. > The -a and -l options are unimportant because nobody should use > telnet(1) with authentication. The -b option is unimportant because > the automatically selected source address is almost always just fine. > > So just > > .Ic telnet > .Op Ar options > .Op Ar host Op port > .Pp > Open a > .Xr telnet 1 > session to the given TCP > .Ar port > on the remote server > .Ar host , > specified by name or IP address. > The > .Ar options > are documented in the > .Xr telnet 1 > manual page. > > seems better to me: precise and concise. > > > .Bd -literal -offset indent > > nsh(p)/!man telnet > > .Ed > > This example is probably superfluous at this point. > Escaping to a shell (i guess that is what "!" means) > ought to be documented in a different part of this manual page, > and apart from that, the example is trivial. > > > any thoughts / advice welcome > > Hope this helps, > Ingo -- Kindest regards, Tom Smyth.
Re: Is there a way to display the block of another man page inside a man page
Hi Tom, Tom Smyth wrote on Mon, May 02, 2022 at 01:46:50AM +0100: > while documenting nsh and its features, > I wanted to display the command switches of telnet command inside the > manual page for nsh, Don't. This is not a technical problem: "how can i technically do this" is the wrong question to ask. This is a problem of manual page design and content organisation. Having a large amount of identical text in two manual pages is a bad idea because readers will wonder whether the text is indeed identical or whether there are subtle differences. They will likely waste time by starting to compare the two pages to track down the differences. Besides, displaying lots of content from one page in another is bad documentation design because it detracts from the topic of the other page. Instead, explain in the other page which content of the first page also applies here, as precisely as possible. > I would like to display , the contents of the > telnet , name synopsis and description sections from the telnet > manpage in the nsh man page without copying the contents of the man > page. (so that the command line switches / arguments are up to date > for a given OpenBSD version > > for now i have done telnet client documentation in nsh as follows > .Tg telnet Most likely, .Tg is not needed right in front of .Ic with the same argument. Does :t telnet not work without it? > .Ic telnet > .Op -a That should be ".Op Fl a"; the same applies below. > .Op -b host-alias > .Op -l user-name > .Ar host-name Just ".Ar host" is enough; it may not even be a name. > .Op Ar port > .Pp > Open a telnet client session to the remote host host-name. Better: Open a .Xr telnet 1 session to the remote server .Ar host , which can be specified by name or IP address. > Where host-name can be a name or IP address of the remote host. > port is the TCP port on the remote host which you wish to connect and port > can be within the range 0-65535. > The > .Ic -a > switch will attempt an automatic login if the setup permits it. > The > .Ic -b host-alias > will bind the source IP telnet client session to a specific ip address alias > rather than the primary ip address on a given interface. > See the > .Xr telnet 1 > man page for a comprehensive list of telnet command options. Yes, that is how to do it. Nits: s/man/manual/; s/command/command line/ I think i would trim this down even more. The -a and -l options are unimportant because nobody should use telnet(1) with authentication. The -b option is unimportant because the automatically selected source address is almost always just fine. So just .Ic telnet .Op Ar options .Op Ar host Op port .Pp Open a .Xr telnet 1 session to the given TCP .Ar port on the remote server .Ar host , specified by name or IP address. The .Ar options are documented in the .Xr telnet 1 manual page. seems better to me: precise and concise. > .Bd -literal -offset indent > nsh(p)/!man telnet > .Ed This example is probably superfluous at this point. Escaping to a shell (i guess that is what "!" means) ought to be documented in a different part of this manual page, and apart from that, the example is trivial. > any thoughts / advice welcome Hope this helps, Ingo
Re: [new] mail/aerc - terminal email client
> It's based on a previous submission by Raymond (+cc). I've enabled the > notmuch support (but not really tried it yet) and updated it, plus some > other minor tweaks. It is working for me with notmuch. I'm sending this with your aerc port. This is my first time using aerc. Thanks for porting it! -- James
Re: READMEs files for ports
On Sun, May 01, 2022 at 09:43:28PM +0200, Marc Espie wrote: > You guys got to remember those are mostly written by developers. > > There's a bit of a chicken problem: when you've been playing with > software for a while, it's difficult to figure out what might be a problem > for newcomers. > > That said READMEs files should reflect stuff that's a good idea to do if > you're using that package PREFERABLY IN A VERY TERSE MANNER. > > If you are using packages YOU CAN HELP. > > Yeah. > > What do you think is hard to figure out and could use a mention in a > pkg-readme ? > > Bear in mind that we're mostly talking OpenBSD specific related stuff. > > But personally, I don't mind a quickstart on "unfriendly" opensource > that's hard to get to work without looking at their docs. > > THIS IS AN OPPORTUNITY PEOPLE!!! > > You are using OpenBSD and you thing it's difficult to contribute ? > > Maybe you can share your experiences about making things work and what was > hard to figure out ? > > (Side note: pkg land is very tricky to automate. Some of what you're going to > say I'm probably already aware of, but nevertheless this might give an idea > about priorities on what to work on first) > dovecot readme says that "various" things need to be increased to make it work. No explanation how to do that. I have a page bookmarked that I have used in the past to be able to do those things in a new installation. I'm clueless about the right numbers. I just guess. postgresql-server seriously needs the defaults and the readme numbers changed. On a small server popping out 300 image file paths, I got terrible errors under mod_perl in the past. For many applications, the low numbers of connections are just fine. But any web server application needs far more. Some advice on what are good numbers for different situations would be a great help. I would love to help with those two, but I genuinely don't know the right answers beyond "I did this and it works". -- Chris Bennett
Is there a way to display the block of another man page inside a man page
Hello, while documenting nsh and its features, I wanted to display the command switches of telnet command inside the manual page for nsh, I would like to display , the contents of the telnet , name synopsis and description sections from the telnet manpage in the nsh man page without copying the contents of the man page. (so that the command line switches / arguments are up to date for a given OpenBSD version for now i have done telnet client documentation in nsh as follows .Tg telnet .Ic telnet .Op -a .Op -b host-alias .Op -l user-name .Ar host-name .Op Ar port .Pp Open a telnet client session to the remote host host-name. Where host-name can be a name or IP address of the remote host. port is the TCP port on the remote host which you wish to connect and port can be within the range 0-65535. The .Ic -a switch will attempt an automatic login if the setup permits it. The .Ic -b host-alias will bind the source IP telnet client session to a specific ip address alias rather than the primary ip address on a given interface. See .Xr telnet 1 man page for a comprehensive list of telnet command options. .Bd -literal -offset indent nsh(p)/!man telnet .Ed any thoughts / advice welcome -- Kindest regards, Tom Smyth.
回复: games/chessx: Update to 1.5.0
ping ... 发件人: wen heping 发送时间: 2021年8月13日 8:53 收件人: ports@openbsd.org 主题: games/chessx: Update to 1.5.0 Hi, ports@: Here is a patch for games/chessx to update to 1.5.0. It build and run well on amd64-current system. No tests defined and no other ports depend on it. Cheers ! wen
games/py-chess: Update to 1.9.0
ping ...
发件人: wen heping
发送时间: 2022年4月3日 10:33
收件人: ports@openbsd.org
主题: tsgames/py-chess: Update to 1.9.0
Hi, ports@:
Here is a simple patch for games/py-chess to update to 1.9.0.
It build well and pass all tests on amd64-7.1 system.
No other ports depends on it.
wen
Index: Makefile
===
RCS file: /cvs/ports/games/py-chess/Makefile,v
retrieving revision 1.4
diff -u -p -r1.4 Makefile
--- Makefile11 Mar 2022 19:04:50 - 1.4
+++ Makefile3 Apr 2022 02:29:37 -
@@ -1,6 +1,6 @@
COMMENT = pure Python chess library
-MODPY_EGG_VERSION =1.8.0
+MODPY_EGG_VERSION =1.9.0
DISTNAME = chess-${MODPY_EGG_VERSION}
PKGNAME = py-${DISTNAME}
Index: distinfo
===
RCS file: /cvs/ports/games/py-chess/distinfo,v
retrieving revision 1.2
diff -u -p -r1.2 distinfo
--- distinfo24 Dec 2021 01:41:02 - 1.2
+++ distinfo3 Apr 2022 02:29:37 -
@@ -1,2 +1,2 @@
-SHA256 (chess-1.8.0.tar.gz) = b6VtiDdiR8gZPmrQPBDiwAZvKoGZ+vihWHcYI4kQxUc=
-SIZE (chess-1.8.0.tar.gz) = 6069346
+SHA256 (chess-1.9.0.tar.gz) = d5GDMxLKkwghpBXQHlt0Ppn7VA1lyubMoOArpqNSpFI=
+SIZE (chess-1.9.0.tar.gz) = 6070330
回复: x11/lxqt: Update to 1.1.0
Agree.
发件人: Rafael Sadowski
发送时间: 2022年5月1日 22:53
收件人: wen heping
抄送: ports@openbsd.org
主题: Re: x11/lxqt: Update to 1.1.0
On Sun May 01, 2022 at 02:13:13PM +, wen heping wrote:
> Hi, ports@:
>
>Here is a patch for x11/lxqt to update to 1.1.0.
>It build well and run well on my amd64-7.1 system.
>
>Any comments?
We could replace:
+LIB_DEPENDS += x11/lxqt/liblxqt>=1.1.0
with
+LIB_DEPENDS += x11/lxqt/liblxqt>=${VERSION}
What do you think?
Rafael
Re: [NEW] sysutils/fd
On Fri, Apr 29, 2022 at 09:48:16AM +0200, Theo Buehler wrote: > > Here is a new port: sysutils/fd > > > > I was a bit skeptical at first about why a find replacement was useful, > > but speed alone won me over. > > I'm ok with importing this, but I'd like to see two changes: 1. add > > MODCARGO_BUILD_ARGS = --no-default-features > > to disable the use of jemalloc instead of system malloc and 2. it would > be nice if you could take MAINTAINER to reduce the burden on semarie for > Rust updates. Makes sense, thanks for spotting this. Imported with both changes in.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2022/05/01 15:12:11 Modified files: sysutils : Makefile Log message: Add fd.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2022/05/01 15:11:16 Log message: Import sysutils/fd. fd is a program to find entries in your filesystem. It is a simple, fast and user-friendly alternative to find. While it does not aim to support all of find's powerful functionality, it provides sensible (opinionated) defaults for a majority of use cases. OK tb@, rsadowski@ Status: Vendor Tag: fcambus Release Tags: fcambus_20220501 N ports/sysutils/fd/Makefile N ports/sysutils/fd/crates.inc N ports/sysutils/fd/distinfo N ports/sysutils/fd/pkg/PLIST N ports/sysutils/fd/pkg/DESCR No conflicts created by this import
Re: [ports discussion] enforcing maintainership?
I think that, for one port that I'm maintainer or, there are probably 10+ ports I originated/did major changes on. One thing Solene is right about: what does port maintainership means ? It means there's one person who cares deeply enough about the port that he's going to keep it (more or less) up-to-date and will be the go-to person for changes to that port. As it stands, I don't think "multi-maintainer" ports are a solution. I also don't think keeping everything squeaky up-to-date is the solution either. And finally (surprise!) I don't think that removing ports without recent activity is the solution either. The way Unix works, we got 5000+ ports that don't need much activity nor maintainership. Some of them might be somewhat out-of-date but this doesn't have huge implications, security-wise. The remaining 5000 split among stuff that's trivial to maintain (meaning: it's in good enough shape/portable enough that an update can be done by anyone) and stuff that's trickier. I think the main goal we should have is to get more people on-board. Face it: we are lagging behind badly when it comes to gettin more ports aboard. Yeah, there's the question of quality and all that. Let me wonder a bit. We've got all kinds of tools to catch bad mistakes these days. What's wrong with opening the Ivory Tower a wee little bit more and getting more ports people ? Newcomers may make mistakes. We got more tools to catch those mistakes. And we need tooling for that. More people to work with -> more time to work on stuff that needs working on.
READMEs files for ports
You guys got to remember those are mostly written by developers. There's a bit of a chicken problem: when you've been playing with software for a while, it's difficult to figure out what might be a problem for newcomers. That said READMEs files should reflect stuff that's a good idea to do if you're using that package PREFERABLY IN A VERY TERSE MANNER. If you are using packages YOU CAN HELP. Yeah. What do you think is hard to figure out and could use a mention in a pkg-readme ? Bear in mind that we're mostly talking OpenBSD specific related stuff. But personally, I don't mind a quickstart on "unfriendly" opensource that's hard to get to work without looking at their docs. THIS IS AN OPPORTUNITY PEOPLE!!! You are using OpenBSD and you thing it's difficult to contribute ? Maybe you can share your experiences about making things work and what was hard to figure out ? (Side note: pkg land is very tricky to automate. Some of what you're going to say I'm probably already aware of, but nevertheless this might give an idea about priorities on what to work on first)
Re: NEW: x11/qt6/qtmultimedia
On 2022/05/01 20:36, Rafael Sadowski wrote:
> OK?
>
> Information for inst:qt6-qtmultimedia-6.3.0
>
> Comment:
> Qt6 multimedia components
>
> Description:
> Qt Multimedia is an add-on module that provides a rich set of QML types and
> C++
> classes to handle multimedia content. It contains an easy to use API for
> playing back audio and video files and rendering those on screen, as well as a
> comprehensive API for recording audio and video from the systems cameras and
> microphones.
>
> Maintainer: The OpenBSD ports mailing-list
>
> WWW: https://www.qt.io/
>
>
ok.
: BUILD_DEPENDS = audio/pulseaudio \
: x11/qt6/qtsvg>=${VERSION},<${NEXT_VERSION}
:
: LIB_DEPENDS = devel/glib2 \
: multimedia/gstreamer1/core \
: multimedia/gstreamer1/plugins-base \
: multimedia/gstreamer1/plugins-bad \
: x11/qt6/qtdeclarative>=${VERSION},<${NEXT_VERSION}
have you considered setting PKGSPEC in x11/qt6/qtdeclarative and
x11/qt6/qtsvg (and the others with this construct) instead?
it sets the default automatically for any ports depending on it.
NEW: x11/qt6/qtmultimedia
OK? Information for inst:qt6-qtmultimedia-6.3.0 Comment: Qt6 multimedia components Description: Qt Multimedia is an add-on module that provides a rich set of QML types and C++ classes to handle multimedia content. It contains an easy to use API for playing back audio and video files and rendering those on screen, as well as a comprehensive API for recording audio and video from the systems cameras and microphones. Maintainer: The OpenBSD ports mailing-list WWW: https://www.qt.io/ qt6-qtmultimedia-6.3.0.tar.gz Description: Binary data
UPDATE: x11/xscope 1.4.2
Hi,
This updates xscope to version 1.4.2. Patch has been submitted
upstreams:
https://gitlab.freedesktop.org/xorg/app/xscope/-/merge_requests/6
ok?
Index: Makefile
===
RCS file: /cvs/OpenBSD/ports/x11/xscope/Makefile,v
retrieving revision 1.4
diff -u -p -u -r1.4 Makefile
--- Makefile11 Mar 2022 20:18:09 - 1.4
+++ Makefile1 May 2022 16:47:28 -
@@ -1,5 +1,5 @@
COMMENT = X Window Protocol Viewer
-DISTNAME = xscope-1.4.1
+DISTNAME = xscope-1.4.2
CATEGORIES = x11
HOMEPAGE = http://wiki.X.Org/
Index: distinfo
===
RCS file: /cvs/OpenBSD/ports/x11/xscope/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -u -r1.1.1.1 distinfo
--- distinfo13 Jul 2014 08:19:53 - 1.1.1.1
+++ distinfo1 May 2022 16:47:47 -
@@ -1,2 +1,2 @@
-SHA256 (xscope-1.4.1.tar.gz) = +ZVYpk6CjNLDUgke02KtLvQrHFXvXAHL94K+lzW7beM=
-SIZE (xscope-1.4.1.tar.gz) = 278083
+SHA256 (xscope-1.4.2.tar.gz) = 4S1jSmnOHsNrCv0dQIFCFeJigBoDDd+D19A0jNBGs4E=
+SIZE (xscope-1.4.2.tar.gz) = 280923
Index: patches/patch-peerinfo_c
===
RCS file: patches/patch-peerinfo_c
diff -N patches/patch-peerinfo_c
--- /dev/null 1 Jan 1970 00:00:00 -
+++ patches/patch-peerinfo_c1 May 2022 16:58:51 -
@@ -0,0 +1,15 @@
+Index: peerinfo.c
+--- peerinfo.c.orig
peerinfo.c
+@@ -43,7 +43,11 @@ static pid_t
+ GetPidFromFd(FD fd)
+ {
+ #ifdef SO_PEERCRED
++#ifndef __OpenBSD__
+ struct ucred cred;
++#else
++struct sockpeercred cred;
++#endif
+ socklen_t cred_len = sizeof(cred);
+
+ if (getsockopt(fd, SOL_SOCKET, SO_PEERCRED, , _len) == 0 &&
--
Matthieu Herrb
NEW: x11/qt6/qtwayland
Information for inst:qt6-qtwayland-6.3.0 Comment: Wayland support for Qt6 Description: QtWayland is a Qt module that wraps the functionality of Wayland. QtWayland is separated into a client and server side. The client side is the wayland platform plugin, and provides a way to run Qt applications as Wayland clients. The server side is the Qt Wayland Compositor API, and allows users to write their own Wayland compositors. Maintainer: The OpenBSD ports mailing-list WWW: https://www.qt.io/ qt6-qtwayland-6.3.0.tar.gz Description: Binary data
Re: x11/lxqt: Update to 1.1.0
On Sun May 01, 2022 at 02:13:13PM +, wen heping wrote:
> Hi, ports@:
>
>Here is a patch for x11/lxqt to update to 1.1.0.
>It build well and run well on my amd64-7.1 system.
>
>Any comments?
We could replace:
+LIB_DEPENDS += x11/lxqt/liblxqt>=1.1.0
with
+LIB_DEPENDS += x11/lxqt/liblxqt>=${VERSION}
What do you think?
Rafael
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: ben...@cvs.openbsd.org 2022/05/01 08:48:13 Modified files: www/p5-WWW-Form-UrlEncoded-XS: Makefile distinfo www/p5-WWW-Form-UrlEncoded-XS/pkg: PLIST Log message: Update to p5-WWW-Form-UrlEncoded-XS-0.27 from wen heping.
www/p5-WWW-Form-UrlEncoded-XS: Update to 0.27
Hi, ports@:
Here is a simple patch for www/p5-WWW-Form-UrlEncoded-XS
to update to 0.27. It build well and pass all tests on amd64-7.1 suystem.
Only one port depends on it: www/p5-WWW-Form-UrlEncoded.
It build well and pass all tests too.
Upstream Changes for version 0.27 - 2022-04-14
Fixed segfault.
wen Index: Makefile
===
RCS file: /cvs/ports/www/p5-WWW-Form-UrlEncoded-XS/Makefile,v
retrieving revision 1.4
diff -u -p -r1.4 Makefile
--- Makefile16 Mar 2022 10:16:34 - 1.4
+++ Makefile1 May 2022 14:26:25 -
@@ -1,9 +1,8 @@
COMMENT = parser and builder for x-www-form-urlencoded in XS
-DISTNAME = WWW-Form-UrlEncoded-XS-0.26
+DISTNAME = WWW-Form-UrlEncoded-XS-0.27
CATEGORIES = www
MODULES = cpan
-REVISION = 0
# Perl
PERMIT_PACKAGE = Yes
Index: distinfo
===
RCS file: /cvs/ports/www/p5-WWW-Form-UrlEncoded-XS/distinfo,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 distinfo
--- distinfo6 Jul 2019 20:34:17 - 1.1.1.1
+++ distinfo1 May 2022 14:26:25 -
@@ -1,2 +1,2 @@
-SHA256 (WWW-Form-UrlEncoded-XS-0.26.tar.gz) =
l6L9QdBEqzuawq9qdC65SqtQUjWtKtr/U1Sj8CdupzE=
-SIZE (WWW-Form-UrlEncoded-XS-0.26.tar.gz) = 58649
+SHA256 (WWW-Form-UrlEncoded-XS-0.27.tar.gz) =
SiEggMysnT7dX9FK9wEDi2QN1pdPG8oJQBThhTK/KjA=
+SIZE (WWW-Form-UrlEncoded-XS-0.27.tar.gz) = 58761
Index: pkg/PLIST
===
RCS file: /cvs/ports/www/p5-WWW-Form-UrlEncoded-XS/pkg/PLIST,v
retrieving revision 1.2
diff -u -p -r1.2 PLIST
--- pkg/PLIST 11 Mar 2022 20:10:38 - 1.2
+++ pkg/PLIST 1 May 2022 14:26:25 -
@@ -8,5 +8,5 @@ ${P5ARCH}/auto/WWW/
${P5ARCH}/auto/WWW/Form/
${P5ARCH}/auto/WWW/Form/UrlEncoded/
${P5ARCH}/auto/WWW/Form/UrlEncoded/XS/
-${P5ARCH}/auto/WWW/Form/UrlEncoded/XS/XS.so
+@so ${P5ARCH}/auto/WWW/Form/UrlEncoded/XS/XS.so
@man man/man3p/WWW::Form::UrlEncoded::XS.3p
x11/lxqt: Update to 1.1.0
Hi, ports@:
Here is a patch for x11/lxqt to update to 1.1.0.
It build well and run well on my amd64-7.1 system.
Any comments?
Cheers !
wenIndex: Makefile.inc
===
RCS file: /cvs/ports/x11/lxqt/Makefile.inc,v
retrieving revision 1.7
diff -u -p -r1.7 Makefile.inc
--- Makefile.inc11 Mar 2022 20:16:38 - 1.7
+++ Makefile.inc1 May 2022 14:07:55 -
@@ -1,6 +1,6 @@
DIST_SUBDIR = lxqt
-VERSION ?= 1.0.0
+VERSION ?= 1.1.0
DISTNAME ?=${NAME}-${VERSION}
Index: about/Makefile
===
RCS file: /cvs/ports/x11/lxqt/about/Makefile,v
retrieving revision 1.8
diff -u -p -r1.8 Makefile
--- about/Makefile 11 Mar 2022 20:16:38 - 1.8
+++ about/Makefile 1 May 2022 14:07:55 -
@@ -6,7 +6,7 @@ WANTLIB += ${COMPILER_LIBCXX} KF5WindowS
WANTLIB += Qt5Gui Qt5Svg Qt5Widgets Qt5X11Extras Qt5Xdg Qt5XdgIconLoader
WANTLIB += Qt5Xml X11 c gio-2.0 glib-2.0 gobject-2.0 lxqt m
-LIB_DEPENDS += x11/lxqt/liblxqt>=1.0.0
+LIB_DEPENDS += x11/lxqt/liblxqt>=1.1.0
BUILD_DEPENDS += x11/lxqt/build-tools
Index: about/distinfo
===
RCS file: /cvs/ports/x11/lxqt/about/distinfo,v
retrieving revision 1.3
diff -u -p -r1.3 distinfo
--- about/distinfo 22 Nov 2021 05:45:42 - 1.3
+++ about/distinfo 1 May 2022 14:07:55 -
@@ -1,2 +1,2 @@
-SHA256 (lxqt/lxqt-about-1.0.0.tar.xz) =
HBT2i/ZQmfvUawYv/GySZWYgqhqe7FoP0tGxGIiTkgM=
-SIZE (lxqt/lxqt-about-1.0.0.tar.xz) = 43176
+SHA256 (lxqt/lxqt-about-1.1.0.tar.xz) =
g1u8WORU2x/EY88/9lMmlRQApPn/W03osOo62+6CeA0=
+SIZE (lxqt/lxqt-about-1.1.0.tar.xz) = 45324
Index: build-tools/Makefile
===
RCS file: /cvs/ports/x11/lxqt/build-tools/Makefile,v
retrieving revision 1.10
diff -u -p -r1.10 Makefile
--- build-tools/Makefile19 Apr 2022 13:06:37 - 1.10
+++ build-tools/Makefile1 May 2022 14:07:55 -
@@ -1,7 +1,6 @@
COMMENT = various packaging tools and scripts for LXQt applications
-VERSION = 0.10.0
-REVISION = 1
+VERSION = 0.11.0
NAME = lxqt-build-tools
Index: build-tools/distinfo
===
RCS file: /cvs/ports/x11/lxqt/build-tools/distinfo,v
retrieving revision 1.3
diff -u -p -r1.3 distinfo
--- build-tools/distinfo22 Nov 2021 05:45:42 - 1.3
+++ build-tools/distinfo1 May 2022 14:07:55 -
@@ -1,2 +1,2 @@
-SHA256 (lxqt/lxqt-build-tools-0.10.0.tar.xz) =
+suGsL871P0gMG066WWhSO1ZeF6vfXMWmoKpdHPQO+o=
-SIZE (lxqt/lxqt-build-tools-0.10.0.tar.xz) = 25312
+SHA256 (lxqt/lxqt-build-tools-0.11.0.tar.xz) =
3V1J5Z+bBVLLQBGOsopGP2MLXebmJrKRBBC1TvO8wbk=
+SIZE (lxqt/lxqt-build-tools-0.11.0.tar.xz) = 25348
Index: build-tools/patches/patch-cmake_find-modules_FindGLIB_cmake
===
RCS file: build-tools/patches/patch-cmake_find-modules_FindGLIB_cmake
diff -N build-tools/patches/patch-cmake_find-modules_FindGLIB_cmake
--- build-tools/patches/patch-cmake_find-modules_FindGLIB_cmake 13 Apr 2022
06:01:59 - 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -
@@ -1,17 +0,0 @@
-From 62b77bb807aa2ac2c1df8eec372df771da8d2203 Mon Sep 17 00:00:00 2001
-From: Dmitry Shachnev
-Date: Tue, 29 Mar 2022 00:29:49 +0300
-Subject: [PATCH] Replace gunixconnection.h file in gio-unix include dir check
(#74)
-
-Index: cmake/find-modules/FindGLIB.cmake
cmake/find-modules/FindGLIB.cmake.orig
-+++ cmake/find-modules/FindGLIB.cmake
-@@ -101,7 +101,7 @@ foreach (_component ${GLIB_FIND_COMPONENTS})
- elseif (${_component} STREQUAL "gio-unix")
- pkg_check_modules(GIO_UNIX gio-unix-2.0)
- find_path(GLIB_GIO_UNIX_INCLUDE_DIR
-- NAMES gio/gunixconnection.h
-+ NAMES gio/gunixfdlist.h
- HINTS ${GIO_UNIX_INCLUDEDIR}
- PATH_SUFFIXES gio-unix-2.0)
-
Index: compton-conf/Makefile
===
RCS file: /cvs/ports/x11/lxqt/compton-conf/Makefile,v
retrieving revision 1.7
diff -u -p -r1.7 Makefile
--- compton-conf/Makefile 11 Mar 2022 20:16:39 - 1.7
+++ compton-conf/Makefile 1 May 2022 14:07:55 -
@@ -1,7 +1,6 @@
COMMENT = configuration tool for compton X composite manager
-VERSION = 0.15.0
-REVISION = 0
+VERSION = 0.16.0
NAME = compton-conf
Index: compton-conf/distinfo
===
RCS file: /cvs/ports/x11/lxqt/compton-conf/distinfo,v
retrieving revision 1.2
diff -u -p -r1.2 distinfo
--- compton-conf/distinfo 4 Sep 2020 15:40:10 - 1.2
+++ compton-conf/distinfo 1 May 2022 14:07:55 -
@@ -1,2 +1,2 @@
-SHA256
Re: NEW: textproc/qpdfview-0.4.18
On 1 May 2022 15:52:11 CEST, Salil Wadnerkar wrote: >Ping. > >On Thu, Apr 28, 2022, 1:29 PM Salil Wadnerkar wrote: > >> Hi Stuart and Omar, >> >> Thank you for your review. I have made the changes and checked that the >> port is working. >> Please find it attached. >> >> Best regards, >> Salil >> >> >> On Thu, Apr 28, 2022 at 12:44 PM Stuart Henderson >> wrote: >> >>> On 2022/04/25 11:18, Omar Polo wrote: >>> > to be. That said I'm a little hesintat to import something that hasn't >>> > been updated in the last ten years... >>> >>> Still developed it seems, but no recent releases >>> >>> https://answers.launchpad.net/qpdfview/+question/701094 >>> >>> regarding the port, s/Tab/tab/ in COMMENT, and some things are set >>> by the qt5 module and should be removed from this port: the COMPILER >>> line, and the LIB_DEPENDS on x11/qt5/qtbase >>> >>> it was imported two days ago by sthen@, see http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/textproc/qpdfview/ and should be come available in -CURRENT soon (if it's not already) and in the next stable release thanks, Omar Polo -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: abie...@cvs.openbsd.org 2022/05/01 08:01:42 Modified files: net/tailscale : Makefile distinfo modules.inc Log message: Update to 1.24.2 Set version info when building.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: abie...@cvs.openbsd.org 2022/05/01 08:00:13 Modified files: audio/shairport-sync: Makefile audio/shairport-sync/pkg: PLIST README Log message: Add README talking about sndio cookies. Diff from Paul de Weerd (Thanks Paul!!), OK sthen
Re: NEW: textproc/qpdfview-0.4.18
Ping. On Thu, Apr 28, 2022, 1:29 PM Salil Wadnerkar wrote: > Hi Stuart and Omar, > > Thank you for your review. I have made the changes and checked that the > port is working. > Please find it attached. > > Best regards, > Salil > > > On Thu, Apr 28, 2022 at 12:44 PM Stuart Henderson > wrote: > >> On 2022/04/25 11:18, Omar Polo wrote: >> > to be. That said I'm a little hesintat to import something that hasn't >> > been updated in the last ten years... >> >> Still developed it seems, but no recent releases >> >> https://answers.launchpad.net/qpdfview/+question/701094 >> >> regarding the port, s/Tab/tab/ in COMMENT, and some things are set >> by the qt5 module and should be removed from this port: the COMPILER >> line, and the LIB_DEPENDS on x11/qt5/qtbase >> >>
Re: UPDATE: fonts/unifont 14.0.02 => 14.0.03
On 4/18/2022 9:27 AM, Brian Callahan wrote: > Hi ports -- > > Attached is an update to GNU Unifont. The biggest user-facing change for > most of us is the inclusion of OTF fonts. Upstream says they may one day > remove the TTF fonts. But until then, I don't see the harm in including > both OTF and TTF fonts. > > OK? > > ~Brian Ping.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2022/05/01 07:02:48 Modified files: www/w3m: Makefile Log message: unbreak w3m's image flavour, reported by naddy
NEW: x11/qt6/qtimageformats
Information for inst:qt6-qtimageformats-6.3.0 Comment: Qt6 additional image formats Description: The core Qt Gui library by default supports reading and writing image files of the most common file formats: PNG, JPEG, BMP, GIF and a few more, ref. Reading and Writing Image Files. The Qt Image Formats add-on module provides optional support for ICNS, JP2, MNG, TGA, TIFF, WBMP, WEBP file formats. Maintainer: The OpenBSD ports mailing-list WWW: https://www.qt.io/ qt6-qtimageformats-6.3.0.tar.gz Description: Binary data
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: rob...@cvs.openbsd.org 2022/05/01 06:53:58 Removed files: mail/kopano/core/patches: patch-php-ext_tests_run-tests_php Log message: remove bogous patch; from aja@
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2022/05/01 05:43:20 Modified files: devel/elfcat : Makefile Log message: Take maintainership for elfcat, I packaged it during h2k21.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: fcam...@cvs.openbsd.org 2022/05/01 05:42:40 Modified files: net/dbip : Makefile.inc net/dbip/asn : distinfo net/dbip/city : distinfo net/dbip/country: distinfo Log message: Update dbip to 2022.05.
aarch64 bulk build report
bulk build on arm64.ports.openbsd.org started on Fri Apr 29 00:57:49 MDT 2022 finished at Sun May 1 05:18:10 MDT 2022 lasted 2D04h20m done with kern.version=OpenBSD 7.1-current (GENERIC.MP) #1637: Thu Apr 28 13:18:00 MDT 2022 built packages:11035 Apr 29:3909 Apr 30:3121 May 1:4004 critical path missing pkgs: http://build-failures.rhaalovely.net/aarch64/2022-04-29/summary.log build failures: 3 http://build-failures.rhaalovely.net/aarch64/2022-04-29/mail/gmime30.log http://build-failures.rhaalovely.net/aarch64/2022-04-29/net/minio/server.log http://build-failures.rhaalovely.net/aarch64/2022-04-29/www/varnish.log recurrent failures failures/net/minio/server.log new failures +++ ls-failures Sun May 1 05:18:21 2022 +failures/mail/gmime30.log +failures/www/varnish.log resolved failures --- ../old/aarch64/last//ls-failuresSat Apr 23 19:05:26 2022 -failures/devel/quirks.log
Re: [ports discussion] enforcing maintainership?
On 2022/05/01 01:01, Marc Espie wrote: > On Sat, Apr 30, 2022 at 08:43:13PM +0100, Stuart Henderson wrote: > > On 2022/04/30 16:37, Solène Rapenne wrote: > > > Hi, > > > > > > I don't know if it has been debated before but I'd like to propose a > > > change, or at least discuss about it. > > > > > > - people submitting new ports must become maintainer > > > > > > - ports without a maintainer must find a maintainer > > > > > > - ports where the maintainer is getting removed or not answering MUST > > > find a new maintainer > > > > strong dislike. > > > I'm with Stuart on this, but I will elaborate. > > Our current problem is having enough developers to handle the flow of ports. > > As far as porting new stuff/updating stuff goes, sometimes people will do > the work, but do not want to commit to maintainership. If we try to enforce > that, we may actually push some people away. > > I don't see any real problem this would solve. > > In an ideal world, we would have three times as many dedicated people curating > the tree. But we want relevant ports to keep coming. > Also, a port with an unresponsive maintainer is a block to someone else doing work in ports (either the port itself, or another one which requires changes in some port). You might say this covers it: > > > - ports where the maintainer is getting removed or not answering MUST > > > find a new maintainer But then what if nobody wants to take maintainer for something which is a dependency of a bunch of other ports? Remove them all? Who is going to do that? It's actually quite delicate work. For ports which I have written, I tend to take maintainer if I want to review changes to that port (either something I use fairly often, maybe in production) or know that it's a tricky one, otherwise I often won't because I don't want to block other people working on it.
CVS: cvs.openbsd.org: ports
CVSROOT:/cvs Module name:ports Changes by: st...@cvs.openbsd.org 2022/05/01 02:51:45 Modified files: mail/mutt : Makefile distinfo Log message: update to mutt-2.2.4
