On 2017-12-10, Stefan Esser wrote:
> Debugging shell scripts is a lot of work, since you cannot
> single step through them.
There are a few shell debuggers:
- http://bashdb.sourceforge.net/
- https://github.com/rocky/kshdb/
- https://github.com/rocky/zshdb/
However none of them is for plain
On Sun, 10 Dec 2017 22:33:25 +0100
Stefan Esser wrote:
> Am 10.12.17 um 18:47 schrieb Matthieu Volat:
> > They do... but only if you commit and push something (even if it's only
> > a personnal clone). If you just keep the changes on your computer, there's
> > nothing.
> The
Am 10.12.17 um 18:47 schrieb Matthieu Volat:
> They do... but only if you commit and push something (even if it's only
> a personnal clone). If you just keep the changes on your computer, there's
> nothing.
The GitHub master version has changes, that are not yet in any release.
This is irrelevant
On Sat, 09 Dec 2017 02:23:10 -0800
"Chris H" wrote:
> On Sat, 9 Dec 2017 10:25:17 +0100 "Matthieu Volat" said
>
> > On Fri, 8 Dec 2017 14:18:28 +0100
> > Baptiste Daroussin wrote:
> >
> > > On Fri, Dec 08, 2017 at 02:13:09PM
On Sat, 9 Dec 2017 10:25:17 +0100 "Matthieu Volat" said
On Fri, 8 Dec 2017 14:18:28 +0100
Baptiste Daroussin wrote:
> On Fri, Dec 08, 2017 at 02:13:09PM +0100, Alexander Leidinger wrote:
> > Quoting Baptiste Daroussin (from Thu, 7 Dec
On Fri, 8 Dec 2017 14:18:28 +0100
Baptiste Daroussin wrote:
> On Fri, Dec 08, 2017 at 02:13:09PM +0100, Alexander Leidinger wrote:
> > Quoting Baptiste Daroussin (from Thu, 7 Dec 2017 14:54:27
> > +0100):
> >
> > > On Thu, Dec 07, 2017 at 02:49:45PM +0100,
On Fri, Dec 08, 2017 at 02:13:09PM +0100, Alexander Leidinger wrote:
> Quoting Baptiste Daroussin (from Thu, 7 Dec 2017 14:54:27
> +0100):
>
> > On Thu, Dec 07, 2017 at 02:49:45PM +0100, Alexander Leidinger wrote:
>
> > > Alternatively, how would a FreeBSD committer like
Quoting Baptiste Daroussin (from Thu, 7 Dec 2017
14:54:27 +0100):
On Thu, Dec 07, 2017 at 02:49:45PM +0100, Alexander Leidinger wrote:
Alternatively, how would a FreeBSD committer like Stefan or
Torsten or me or whoever gain write access to
Thanks to everyone for replying.
From: Stefan Esser [s...@freebsd.org]
Sent: Tuesday, December 5, 2017 16:35
To: Tatsuki Makino; FreeBSD Ports ML
Subject: Working on FLAVOR support in portmaster
> I'm working on FLAVOR support in portmaster.
Thank you
On Thu, Dec 07, 2017 at 02:49:45PM +0100, Alexander Leidinger wrote:
>
> Quoting Stefan Esser (from Tue, 5 Dec 2017 08:35:55 +0100):
>
> > Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > > By the way, where is the clever way to update to flavor?
> > > I am using portmaster.
>
Quoting Stefan Esser (from Tue, 5 Dec 2017 08:35:55 +0100):
Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
By the way, where is the clever way to update to flavor?
I am using portmaster.
I'm working on FLAVOR support in portmaster. My version did already build
I wonder if
I volunteer to test.
Thanks,
Jim Trigg
On December 5, 2017 4:35:05 AM EST, Torsten Zuehlsdorff
wrote:
>Aloha Stefan,
>On 05.12.2017 08:35, Stefan Esser wrote:
>> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
>>> By the way, where is the clever way to update to flavor?
>>> I
On Tue, 5 Dec 2017 13:48:12 -0600 "Mark Linimon" said
On Tue, Dec 05, 2017 at 08:42:27AM -0800, Chris H wrote:
> IMHO it might be a good idea to make a legacy branch, in the ports
> tree before gutting the pre-NG stuff.
Good lord, people.
The pre-NG stuff has Left The
Stefan Esser writes:
Hi Stefan
> Is it acceptable, to have portmaster stop supporting the old package system?
I think so.
Thanks for your work on this.
Éric Masson
--
Discuter tranquillement avec Michel Guillou???
Je n'ai JAMAIS vu quelqu'un de plus *facho* que ce type.
On 12/4/2017 11:35 PM, Stefan Esser wrote:
> Is it acceptable, to have portmaster stop supporting the old package system?
> AFAIK, there is no way that a modern ports tree with flavor support works
> with a non-PKG_NG infrastructure?
100% yes.
If someone needs pkg_* support for an older tree then
On Tue, Dec 05, 2017 at 08:42:27AM -0800, Chris H wrote:
> IMHO it might be a good idea to make a legacy branch, in the ports
> tree before gutting the pre-NG stuff.
Good lord, people.
The pre-NG stuff has Left The Building. It is not coming back.
The last (even trivial) revision to the pkg_*
Am 05.12.2017 um 08:35 schrieb Stefan Esser:
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
>> By the way, where is the clever way to update to flavor?
>> I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated ports, the FLAVOR parameter
Hi,
On Tue, Dec 05, 2017 at 08:35:55AM +0100, Stefan Esser wrote:
> Is it acceptable, to have portmaster stop supporting the old package system?
> AFAIK, there is no way that a modern ports tree with flavor support works
> with a non-PKG_NG infrastructure?
I also started working on this
On Tue, 5 Dec 2017 03:33:10 -0800 "David Wolfskill" said
On Tue, Dec 05, 2017 at 08:35:55AM +0100, Stefan Esser wrote:
> ...
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated ports, the FLAVOR parameter is passed to build
On Tue, 5 Dec 2017 08:35:55 +0100
Stefan Esser wrote:
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > By the way, where is the clever way to update to flavor?
> > I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already build
> all
> On 5 Dec, 2017, at 0:35, Stefan Esser wrote:
>
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
>> By the way, where is the clever way to update to flavor?
>> I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated
On 12/05/17 02:35, Stefan Esser wrote:
> [...]
> Is it acceptable, to have portmaster stop supporting the old package system?
> AFAIK, there is no way that a modern ports tree with flavor support works
> with a non-PKG_NG infrastructure?
>
> Regards, STefan
> [...]
One vote here for dropping old
On Tue, Dec 05, 2017 at 08:35:55AM +0100, Stefan Esser wrote:
> ...
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated ports, the FLAVOR parameter is passed to build sub-processes,
> but there is still some confusion between multiple flavored versions of the
> On 05.12.2017 08:35, Stefan Esser wrote:
> > Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > > By the way, where is the clever way to update to flavor?
> > > I am using portmaster.
> > I'm working on FLAVOR support in portmaster. My version did already build
> > all updated ports, the FLAVOR
Aloha Stefan,
On 05.12.2017 08:35, Stefan Esser wrote:
Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
By the way, where is the clever way to update to flavor?
I am using portmaster.
I'm working on FLAVOR support in portmaster. My version did already build
all updated ports, the FLAVOR parameter
On Tue, 5 Dec 2017 08:35:55 +0100
Stefan Esser wrote:
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > By the way, where is the clever way to update to flavor?
> > I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already
> build all
26 matches
Mail list logo