Marc, Stuart,
Does that mean it's okay to commit below change?
Index: bsd.port.mk
===
RCS file: /cvs/ports/infrastructure/mk/bsd.port.mk,v
retrieving revision 1.1542
diff -u -p -u -r1.1542 bsd.port.mk
--- bsd.port.mk 26 Jun 2020 11:5
On Tue, Feb 02, 2021 at 11:45:24AM +, Stuart Henderson wrote:
> On 2021/02/02 10:05, Marc Espie wrote:
> > On Sun, Jan 24, 2021 at 09:50:50PM +, Stuart Henderson wrote:
> > > You are correct that it will require bumping every port that has
> > > debug packages. It might be better to only ch
On 2021/02/02 10:05, Marc Espie wrote:
> On Sun, Jan 24, 2021 at 09:50:50PM +, Stuart Henderson wrote:
> > You are correct that it will require bumping every port that has
> > debug packages. It might be better to only change the comment
> > if it's too long (so that existing ones aren't change
On Sun, Jan 24, 2021 at 09:50:50PM +, Stuart Henderson wrote:
> You are correct that it will require bumping every port that has
> debug packages. It might be better to only change the comment
> if it's too long (so that existing ones aren't changed).
Actually, I'm not sure it's strictly requi
You are correct that it will require bumping every port that has
debug packages. It might be better to only change the comment
if it's too long (so that existing ones aren't changed).
Also, you don't need to use the full $prefix.0.$date.git.$sha in
the PKGNAME, in particular the sha is likely to b
I didn't receive any feedback. Would like to hear your thoughts. As
below diff helps me in certain way, I would like to have this change
incorporated into OpenBSD ports tree.
On Fri, Jan 01, 2021 at 07:53:42PM +, Mikolaj Kucharski wrote:
> Hi,
>
> I often generate my own distfiles from git ch
Hi,
I often generate my own distfiles from git checkout when I debug code
from OpenBSD ports tree. Some of the ports have already debug packages
defined. Sample debug package looks as follows:
# pkg_info -I debug-sane-backends
debug-sane-backends-1.0.31p1 debug info for sane-backends-1.0.31p1
deb
