Re: [ANN] mksh R50f

2015-04-20 Thread Guido Berhoerster
* Thorsten Glaser  [2015-04-20 23:35]:
> Dixi quod…
> 
> >+ed -s mksh.1 <<'EOF'
> >+/insert-your-name-here/s/^\.\\" //
> 
> (Yes, this means I made the feature with your specfile in mind :)

OK cool, I've already added it to the openSUSE specfile.
-- 
Guido Berhoerster


Re: [ANN] mksh R50f

2015-04-20 Thread Thorsten Glaser
Dixi quod…

>+ed -s mksh.1 <<'EOF'
>+/insert-your-name-here/s/^\.\\" //

(Yes, this means I made the feature with your specfile in mind :)

bye,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc


Re: [ANN] mksh R50f

2015-04-20 Thread Thorsten Glaser
Guido Berhoerster dixit:

>where and in what form do you want this vendor info to be added
>to the manpage?

tglase@tglase:~/stuff/OBS/shells/mksh $ osc diff
Index: mksh.spec
===
--- mksh.spec   (revision 182)
+++ mksh.spec   (working copy)
@@ -65,6 +65,11 @@
 ed -s check.t <<'EOF'
 ,s/@(#)\(MIRBSD\|LEGACY\) KSH R\(.*\)/@(#)\1 KSH R\2 SUSE/
 w
+EOF
+ed -s mksh.1 <<'EOF'
+/insert-your-name-here/s/^\.\\" //
+s/insert-your-name-here/SuSE/
+wq
 EOF
 %endif


Thanks,
//mirabilos
-- 
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec


Re: [ANN] mksh R50f

2015-04-20 Thread Guido Berhoerster
Hi,

* Thorsten Glaser  [2015-04-19 21:50]:
> I=E2=80=99d like to take this chance to remember everyone that, when
> patching the source code, to please append something to the
> version (twice in check.t, once in sh.h) and (*new*) once in
> the manpage (mksh.1), so your users will know. For packaging
> I have my hands in, I append a string e.g. =E2=80=9CDebian-7=E2=80=9D for
> the seventh Debian upload for that base version (so that it
> matches the package version, even if the first couple uploads
> were unpatched), i.e. include the vendor and enough of the
> version to be unique.

where and in what form do you want this vendor info to be added
to the manpage?
-- 
Guido Berhoerster