On Fri, May 05, 2023 at 01:18:43PM -0400, Derek Schrock wrote:
> On Fri, May 05, 2023 at 01:04:00AM EDT, Alex Kozlov wrote:
> > I use %I specifier from vvv.initials (QUOTE_PATCH option), but have
> > vvv.quote
> > commented out in the port's Makefile. I don't remember exactly why, it seems
> > cau
On 5/5/23 15:49, Derek Schrock wrote:
On Fri, May 05, 2023 at 06:45:48PM EDT, Edward Sanford Sutton, III wrote:
Not saying what to do but trying to continue to build up my
understanding of ports tree structure in general with my questions.
Wouldn't telling users after install/upgrade be tell
On Fri, May 05, 2023 at 06:45:48PM EDT, Edward Sanford Sutton, III wrote:
>Not saying what to do but trying to continue to build up my
> understanding of ports tree structure in general with my questions.
> Wouldn't telling users after install/upgrade be telling them that there
> is now a pr
On 5/5/23 15:07, Derek Schrock wrote:
On Fri, May 05, 2023 at 06:04:35PM EDT, Amar Takhar wrote:
It would be nice to have a message in pkg-message explaining the port is now
vanilla outside of fixes and anyone looking for former patches should try
NeoMutt.
Yeah, I'm looking right now at adding
On Fri, May 05, 2023 at 06:04:35PM EDT, Amar Takhar wrote:
> It would be nice to have a message in pkg-message explaining the port is now
> vanilla outside of fixes and anyone looking for former patches should try
> NeoMutt.
Yeah, I'm looking right now at adding a pkg-message to output a message
On 2023-05-05 20:19 +0200, Felix Palmen wrote:
>
> So, again IMHO, let's stick to the "only patch ustream when really
> needed to fix something" policy with Mutt as well.
I've used Mutt from the first version when I was eager to switch from Pine. I
have to admit I have never heard of NeoMutt.
On Fri, May 05, 2023 at 01:04:00AM EDT, Alex Kozlov wrote:
> I use %I specifier from vvv.initials (QUOTE_PATCH option), but have vvv.quote
> commented out in the port's Makefile. I don't remember exactly why, it seems
> caused some formatting issues.
It seems you're already building locally? If t
Dear port maintainers,
The portscout new distfile checker has detected that one or more
unmaintained ports appears to be out of date. Please take the opportunity
to check each of the ports listed below, and if possible and appropriate,
submit/commit an update. Please consider also adopting this po
* Colin Percival [20230505 08:12]:
> Older bmake handles ${FOO:%=bar%} with an empty FOO by matching % to the
> empty string. In 2020, NetBSD changed this to non-matching "for gmake
> compatibility".
That's indeed a weak reason, I would have expected the reason to be &qu
On 5/5/23 07:53, Felix Palmen wrote:
* Colin Percival [20230505 07:46]:
On 5/4/23 23:47, Colin Percival wrote:
Indeed. I think I've fixed it by copying a newer /usr/bin/make into the
build environment -- I should be able to confirm whether it works soon.
Confirmed, portsnap'
* Colin Percival [20230505 07:46]:
> On 5/4/23 23:47, Colin Percival wrote:
> > Indeed. I think I've fixed it by copying a newer /usr/bin/make into the
> > build environment -- I should be able to confirm whether it works soon.
>
> Confirmed, portsnap's INDEX is
On 5/4/23 23:47, Colin Percival wrote:
On 5/4/23 02:09, Felix Palmen wrote:
I have a possible update for this commit that avoids the part that
*seems* to be problematic here. It's more verbose now, but probably also
more readable, so, will put this up for review soon.
But probably it still make
12 matches
Mail list logo
