Re: Firefox problem

2023-12-16 Thread chohag
Prasad MN writes: > Does not work for me either -- I am on the latest snapshot and > Firefox fails with the same error as reported on the thread. > Same error for Tor Browser. It just takes patience. Or make. Surely you have a backup computer? The problem was noticed and the patch pushed to CVS o

Re: [NEW] x11/xnotify

2023-01-13 Thread chohag
Omar Polo writes: > removed the sentence "see the manual for more information on how > xnotify works" which - I hope! - should sound obvious :) If wishes were wings... Matthew

Re: Advertising Options / Sponsored Content Options on openports.se

2021-09-22 Thread chohag
Stuart Henderson writes: > (CCs trimmed) > > On 2021/09/21 07:06, Peter Coleman wrote: > > Hi there, > > > >   > > > > We’re currently working on behalf of a major industry-leading client trying > > to enhance their > > brand via editorial content targeting the Swedish Market. > > > >   > > >

Thanks for all the docs; WAS: make documentation

2021-06-27 Thread chohag
Reuben ua Bríġ writes: > > Date: Sun, 27 Jun 2021 15:28:49 +0200 > > From: Ingo Schwarze > > > I literally spent years of my life improving that. > > and im sure it is much better for it. > > ... > > good on em. why is it easier to get third party binaries than the > openbsd source? the whole re

Re: Debug packages policy?

2020-01-21 Thread chohag
Antoine Jacoutot writes: > On Tue, Jan 21, 2020 at 11:57:23AM +, cho...@jtan.com wrote: > > > > > > I don't quite understand your mail. This: > > > > What's the policy for adding debug packages to ports? but ... > See this: > https://man.openbsd.org/bsd.port.mk.5#THE_DEBUG_PACKAGES_INFRAST

Re: Debug packages policy?

2020-01-21 Thread chohag
Antoine Jacoutot writes: > On Mon, Jan 20, 2020 at 11:31:11PM +0100, Christian Weisgerber wrote: > > What's the policy for adding debug packages to ports? > > > > Is the intend to add debug packages... > > * eventually to all ports > > or > > * only to ports where they seem particularly useful? >

Re: [update] stumpwm-19.11

2019-12-16 Thread chohag
Timo Myyrä writes: > > I think the modules are pretty well covered by StumpWM documentation (info > page > / wiki / contrib repo readme). It seems a bit redundant to repeat the same > info > in pkg readme file. Apologies, I must have misunderstood. I was under the impression it was due to an ope

Re: [update] stumpwm-19.11

2019-12-16 Thread chohag
I vaguely recall coming upon this problem some time back and not getting anywhere with it. Might it be worth including this information in the port's readme? Matthew > > Small issue as I was using stumptray in my config, stumpwm > > complains about the lack of xembed even after I updated my > > s

Re: UPDATE: net/telegram-purple

2019-10-30 Thread chohag
Giovanni Bechis writes: > On 10/22/19 6:51 PM, Charlene Wendling wrote: > > On Tue, 22 Oct 2019 08:54:42 +0200 > > Giovanni Bechis wrote: > > > >> On 10/21/19 4:25 PM, Charlene Wendling wrote: > >>> Hi, > >>> > >>> On Sun, 20 Oct 2019 16:02:09 +0200 > >>> Giovanni Bechis wrote: > >>> > Update

Re: When will OpenBSD become a friendly place for bug reporters?

2019-07-09 Thread chohag
Perhaps rather than whining that OpenBSD lacks some specific feature, those who want it could write it? A novel idea, I know, but it IS specifically a development platform and there are precisely zero restrictions. Or if you don't wish to start with code, at least try a tack such as "I intend t

Re: The eternal great desktop thread

2019-05-11 Thread chohag
Theo de Raadt writes: > >> > I recently posted a new CPAN module to ports@ which wraps pledge and > >> > unveil. There was a bit of a balls up because as a sysadmin I'm not > >> > really used to group development and what I've done has usually been in > >> > a corporate environment but in the end a

Re: The eternal great desktop thread

2019-05-10 Thread chohag
Job Snijders writes: > You should consider becoming part of the process, one of the most valuable > currencies you can give to the project is a degree of continuity. > > To phrase it differently, =E2=80=9Cfire and forget=E2=80=9D is rarely a sus= > tainable > approach. Well as suggested I'm not go

Re: The eternal great desktop thread

2019-05-10 Thread chohag
[including ports@] Theo de Raadt writes: > cho...@jtan.com wrote: > > > I recently posted a new CPAN module to ports@ which wraps pledge and > > unveil. There was a bit of a balls up because as a sysadmin I'm not > > really used to group development and what I've done has usually been in > > a cor

Re: p5-Unix-Pledge, this time 0.006

2019-05-01 Thread chohag
... this time I've got my tar incantation correct. Matthew p5-Unix-Pledge-0.006.tgz Description: p5-Unix-Pledge-0.006.tgz

Re: p5-Unix-Pledge, this time 0.006

2019-05-01 Thread chohag
Stuart Henderson writes: > On 2019/05/01 19:42, cho...@jtan.com wrote: > > What would I put in WANTLIB? The only dependency this module has is > > OpenBSD 6.4's base system (well strictly speaking, a libc with the > > pledge and unveil calls). > > WANTLIB += c perl I guess I got unlucky: void:/us

Re: p5-Unix-Pledge, this time 0.006

2019-05-01 Thread chohag
Stuart Henderson writes: > Please send tars not diffs for new ports. Will do. > Missing license marker and WANTLIB. What would I put in WANTLIB? The only dependency this module has is OpenBSD 6.4's base system (well strictly speaking, a libc with the pledge and unveil calls). I can't find examp

p5-Unix-Pledge, this time 0.006

2019-05-01 Thread chohag
I've sat on this for a while because a) my email setup broke when I upgraded my mail client, and b) while I was dealing with that I got a message from the upstream author indicating that he's incorporating my patch, which makes the diff included below an awful lot smaller. On balance, saying that

Re: Port & patch for perl's Unix::Pledge, implementing pledge and unveil

2019-04-18 Thread chohag
Theo de Raadt writes: > cho...@jtan.com wrote: > > > WTFPL 2 leaves upstream completely at liberty to license it under that > > license if they choose. The point of the WTFPL is it's me saying "I've > > written this and you can do what you like with it, up to and including > > literally anything *i

Re: Port & patch for perl's Unix::Pledge, implementing pledge and unveil

2019-04-18 Thread chohag
joshua stein writes: > On Thu, 18 Apr 2019 at 20:59:38 +0300, cho...@jtan.com wrote: > > I've completed a port for Unix::Pledge, a perl module wrapping pledge(2) > > (and now unveil(2)) and would like to know what to do with it. > > > > Unix::Pledge is the lightest-imaginable wrapper around the pl

Port & patch for perl's Unix::Pledge, implementing pledge and unveil

2019-04-18 Thread chohag
I've completed a port for Unix::Pledge, a perl module wrapping pledge(2) (and now unveil(2)) and would like to know what to do with it. Unix::Pledge is the lightest-imaginable wrapper around the pledge system call. The version which the upstream maintainer has released is 0.005, which I've patched