le. Builds and runs fine for me on 7.5,
>> verified with some manual testing.
>>
>> Index: Makefile
>> ===
>> RCS file: /cvs/ports/shells/nsh/Makefile,v
>> diff -u -p -r1.49.2.1 Makefile
>> --- Makefile19 Jun
/ releases out there in the wild...
>
> Here is the diff for -stable. Builds and runs fine for me on 7.5,
> verified with some manual testing.
>
> Index: Makefile
> =======
> RCS file: /cvs/ports/shells/nsh/Makefile,v
es out there in the wild...
Here is the diff for -stable. Builds and runs fine for me on 7.5,
verified with some manual testing.
Index: Makefile
===
RCS file: /cvs/ports/shells/nsh/Makefile,v
diff -u -p -r1.49.2.1 Makefile
--- Makefile
rom stdin nowadays. But since the
>> release was tagged like this I'd rather keep the port aligned with
>> this release's expectations.
>>
>> With the diff below these .sh scripts can be run as Tom documented
>> it in README.md.
>>
>> diff /usr/p
run as Tom documented
> it in README.md.
>
> diff /usr/ports
> commit - f640b88fef18c3032a9b02b089db0dee4d88cf43
> path + /usr/ports
> blob - 66bab971f2124f1025600e908dbb4984214bfd85
> file + shells/nsh/Makefile
> --- shells/nsh/Makefile
> +++ shells/nsh/Makefile
> @@ -2,10 +2,9
b4984214bfd85
file + shells/nsh/Makefile
--- shells/nsh/Makefile
+++ shells/nsh/Makefile
@@ -2,10 +2,9 @@ COMMENT = network switch style shell
CATEGORIES = shells net
HOMEPAGE = https://www.nmedia.net/nsh/
-V =1.2.1
+V =1.2.2
DISTNAME = nsh-${V}
SITES =
other
> save.sh which then breaks packaging. Should the post-install
> target not have an 'rm ${PREFIX}/bin/save.sh'?
>
So I think this is probably the diff we want - this is OK sthen
Index: Makefile
=
b02b089db0dee4d88cf43
path + /usr/ports
blob - 66bab971f2124f1025600e908dbb4984214bfd85
file + shells/nsh/Makefile
--- shells/nsh/Makefile
+++ shells/nsh/Makefile
@@ -2,10 +2,9 @@ COMMENT = network switch style shell
CATEGORIES = shells net
HOMEPAGE = https://www.nmedia.net/nsh/
On Fri, Sep 06, 2024 at 02:04:58PM +0100, Stuart Henderson wrote:
> On 2024/09/06 14:00, Stuart Henderson wrote:
> > ===> Faking installation for nsh-1.2.2
> > install -c -s -o root -g bin -m 755 nsh
> > /pobj/nsh-1.2.2/fake-amd64/usr/local/bin/nsh
> > test -e /usr/local/bin/save.sh || install
On 2024/09/06 14:04, Stuart Henderson wrote:
> On 2024/09/06 14:00, Stuart Henderson wrote:
> > ===> Faking installation for nsh-1.2.2
> > install -c -s -o root -g bin -m 755 nsh
> > /pobj/nsh-1.2.2/fake-amd64/usr/local/bin/nsh
> > test -e /usr/local/bin/save.sh || install -m 755 -o root -g bin
On 2024/09/06 14:00, Stuart Henderson wrote:
> ===> Faking installation for nsh-1.2.2
> install -c -s -o root -g bin -m 755 nsh
> /pobj/nsh-1.2.2/fake-amd64/usr/local/bin/nsh
> test -e /usr/local/bin/save.sh || install -m 755 -o root -g bin
> /usr/obj/ports/nsh-1.2.2/nsh-1.2.2/save-rw.sh /usr
INS@XIeCpSEu4i: Permission denied
*** Error 1 in /usr/obj/ports/nsh-1.2.2/nsh-1.2.2 (Makefile:63 'afterinstall')
On 2024/09/06 14:42, Stefan Sperling wrote:
> Update shells/nsh to 1.2.2.
> Release notes: https://github.com/yellowman/nsh/releases/tag/v1.2.2
>
> Should fix build
a Hard OK from Tom :) ...
Get it in ... get it in :)
thanks folks happy Friday :)
On Fri, 6 Sept 2024 at 13:43, Stefan Sperling wrote:
> Update shells/nsh to 1.2.2.
> Release notes: https://github.com/yellowman/nsh/releases/tag/v1.2.2
>
> Should fix build failures with the -stat
Update shells/nsh to 1.2.2.
Release notes: https://github.com/yellowman/nsh/releases/tag/v1.2.2
Should fix build failures with the -static flavor on sparc64.
Also, make the package provide example scripts which prepare a system for
administration with nsh. These aren't strictly needed i
Thanks Stuart,
Appreciate your help on this...
On Wed, 28 Apr 2021 at 21:24, Stuart Henderson wrote:
>
> On 2021/04/28 20:54, Tom Smyth wrote:
> > Hello,
> >
> > Now that the 6.9 release packages on the mirrors are populated , is it
> > possible for someone to commit the latest diff ? Or is it a
On 2021/04/28 20:54, Tom Smyth wrote:
> Hello,
>
> Now that the 6.9 release packages on the mirrors are populated , is it
> possible for someone to commit the latest diff ? Or is it a case of wait
> for all architecture builds to complete before the changes to nsh can be
> committed?
thanks for t
> > it is compiling cleanly on amd64 6.9 current (20210414 ) without
> > > errors or warnings
> > >
> > > all the patch files in the current port can be removed also as they
> > > have been included or improved upon upstream
> > >
> > > Thanks Chris, Kurt and everyo
gt; > Hello, all,
> > > >
> > > > Chris has incorporated and improved the diffs and merged them upstream,
> > > >
> > > > below is a diff for pulling the latest commit from git
> > > >
> > > > it is compiling cleanly on amd64 6.9
t; > it is compiling cleanly on amd64 6.9 current (20210414 ) without
> > > errors or warnings
> > >
> > > all the patch files in the current port can be removed also as they
> > > have been included or improved upon upstream
> > >
> > > Thanks Chris, Kurt and everyone who helped
upstream
> >
> > Thanks Chris, Kurt and everyone who helped.
> >
> >
> >
> > --
> > Kindest regards,
> > Tom Smyth.
>
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/shells/nsh/Makefile,v
> > retrieving revision 1.41
>
urrent port can be removed also as they
> have been included or improved upon upstream
>
> Thanks Chris, Kurt and everyone who helped.
>
>
>
> --
> Kindest regards,
> Tom Smyth.
> Index: Makefile
> =========
have been included or improved upon upstream
Thanks Chris, Kurt and everyone who helped.
--
Kindest regards,
Tom Smyth.
Index: Makefile
===
RCS file: /cvs/ports/shells/nsh/Makefile,v
retrieving revision 1.41
diff -u -p -r1.41
Thanks Chris,
and thanks for the "variations"
I can see where you were taking a scalpel out where I had used the
sledge hammer :)
Appreciate you accepting and improving the patches
All the best
Tom Smyth
On Wed, 14 Apr 2021 at 21:08, Chris Cappuccio wrote:
>
> I've got all of your changes (or
I've got all of your changes (or variations thereof) in the github repository,
except for the version number change since it isn't quite time to bump yet.
Time to work on the known issues and expand compatibilty with the many features
added in the last 3 or 4 years :)
Tom Smyth [tom.sm...@wireles
Hello,
Please find attached patch for nsh
feedback welcome as my C is rusty,
I hope this helps,
details of proposed patch outlined below
Architectures Compiled on:
AMD64
Compile errors / warnings
1) warning about an unused variable do not want to delete code just yet
2) errors about '\0' Nu
On Mon, 29 Mar 2021 at 02:18, Chris Cappuccio wrote:
> Marc Espie [es...@nerim.net] wrote:
> > I've looked a bit at this code.
> >
> > I'm on the fence between marking it as BROKEN and give Chris a chance to
> > fix the code, or downright removing it.
> >
> > Specifically, it's currently broken t
On Sun, Mar 28, 2021 at 06:14:18PM -0700, Chris Cappuccio wrote:
> Marc Espie [es...@nerim.net] wrote:
> > I've looked a bit at this code.
> >
> > I'm on the fence between marking it as BROKEN and give Chris a chance to
> > fix the code, or downright removing it.
> >
> > Specifically, it's curren
Marc Espie [es...@nerim.net] wrote:
> I've looked a bit at this code.
>
> I'm on the fence between marking it as BROKEN and give Chris a chance to
> fix the code, or downright removing it.
>
> Specifically, it's currently broken thanks to recent changes to if.h,
> but the code warns all over the
Hi All,
as a humble nsh user, I would like to have a go at trying to help with
this port,
we used it in the past and when we reported bugs Chris had resolved them,
I would humbly ask that it not be removed, and Im willing to (try) to see
if I can work through nsh bugs
the idea of nsh is brillia
On 2021-03-22, Marc Espie wrote:
> I'm on the fence between marking it as BROKEN and give Chris a chance to
> fix the code, or downright removing it.
Also, fixes have been limited to keeping up with removals. How
many networking things have been added to OpenBSD over the last
four years?
--
C
I've looked a bit at this code.
I'm on the fence between marking it as BROKEN and give Chris a chance to
fix the code, or downright removing it.
Specifically, it's currently broken thanks to recent changes to if.h,
but the code warns all over the place. There seems to be a misconception
that '\0'
On 2021/03/16 20:03, Christian Weisgerber wrote:
> The recent network changes to inet{4,6} autoconf have broken shells/nsh.
> AGAIN.
> I'm getting rather tired of cleaning this up each time. sthen@ too,
> I think.
Yes, it's not ideal having something so tightly coupled t
The recent network changes to inet{4,6} autoconf have broken shells/nsh.
AGAIN.
I'm getting rather tired of cleaning this up each time. sthen@ too,
I think.
>>> Building on amd64-1 under shells/nsh
Christian Weisgerber [na...@mips.inka.de] wrote:
> The removal of mobileip(4) has broken shells/nsh.
>
> The patches below simply remove mobileip support from nsh and update
> the MANUAL, including a paragraph that became obsolete when mobileip(4)
> was added. I don't use
On 2019/11/06 11:37, Christian Weisgerber wrote:
> The removal of mobileip(4) has broken shells/nsh.
>
> The patches below simply remove mobileip support from nsh and update
> the MANUAL, including a paragraph that became obsolete when mobileip(4)
> was added. I don't use
The removal of mobileip(4) has broken shells/nsh.
The patches below simply remove mobileip support from nsh and update
the MANUAL, including a paragraph that became obsolete when mobileip(4)
was added. I don't use nsh at all, but with this it compiles again.
ok?
Index: Mak
Sorry I didn't get back to you on this earlier. The time_t stuff is
already updated in github. But it all looks fine to me.
Chris
This fixes the build of shells/nsh after the n2k14 network header
changes. While there, I belatedly corrected a number of type
mismatches due to the time_t change.
ok?
Index: Makefile
===
RCS file: /cvs/ports/shells/nsh/Makefile,v
38 matches
Mail list logo
