Re: [dev] less(1) replacement?

[Eric Pruitt]

On Fri, Aug 25, 2017 at 07:37:56PM +, fao_ wrote:
> > 9base is not intended for interactive use, so no, p does not really
> > belong into 9base. 9base is intended to be a scripting environment.
>
> Excuse me if this is a stupid question, but: What's the difference?

Interactive: things that use ncurses, terminfo, termcap, etc.

Scripting: programs like sed, ed, awk, grep, etc. These programs are
often used in the context of larger tasks with pipes for transforming /
processing data.

Eric

[dev] [9base] [musl] "Undefined reference to sigsetjmp"

[fao_]

When compiling 9base with


 CC=musl-gcc
 PREFIX=""
 OBJTYPE=x86_64


I get the error:


 ../lib9/lib9.a(notify.o): In function `signotify`:
 notify.c:(.text+0x9a): undefined reference to `sigsetjmp`
 collect2: error: ld returned 1 exit status


Except:
$ grep -Rni "sigsetjmp" /usr/lib/musl/

 /usr/lib/musl/include/setjmp.h:22:int sigsetjmp (sigjmp_buf, int);
 ...


On the offchance that `setjmp.h` was not included in `notify.c`, I
added it manually. It still failed with the same error.

--
- fao_
PGP fingerprint: 739B 6C5C 3DE1 33FA
"Too enough is always not much!"

Re: [dev] less(1) replacement?

[fao_]

On 2017-08-24 1:50 pm, Anselm R Garbe wrote:

On 24 August 2017 at 13:33, Greg Reagle  wrote:

On Thu, Aug 24, 2017, at 05:01, Anselm R Garbe wrote:

On 24 August 2017 at 01:59, fao_  wrote:
> Is the suckless project packing a replacement to my favorite pager,
> less(1)? Or is the advice to just use something like screen or tmux. I
> don't really want to bother installing and learning those when `less` meets
> my needs perfectly.
>
> As far as I can tell, there isn't. But I could have missed something, given
> how many unrelated results `suckless "less"` pulls up :)

https://github.com/9fans/plan9port/blob/master/src/cmd/p.c


That p command does not seem to be in 9base.  Do the 9base developers
think that it should be?


9base is not intended for interactive use, so no, p does not really
belong into 9base. 9base is intended to be a scripting environment.

BR,
Anselm


Excuse me if this is a stupid question, but: What's the difference?

--
- fao_
PGP fingerprint: 739B 6C5C 3DE1 33FA
"Too enough is always not much!"

Re: [dev] Question about arg.h

[Daniel Xu]

Hi Laslo,

Thanks for the clarification. I have to say it's definitely a different
experience getting used to suckless code.

Dan

On Thu, Aug 24, 2017, at 06:13 AM, Laslo Hunhold wrote:
> On Wed, 23 Aug 2017 20:28:12 -0500
> Daniel Xu  wrote:
> 
> Hey Daniel,
> 
> > I'm currently familiarizing myself with various pieces of suckless
> > code. One thing keeps bothering me, though:
> > 
> > What is EARGF() and ARGF() shorthand for? I can more or less tell what
> > they do but the best I can come up with is "Error arg flag" and "Arg
> > flag", respectively.
> 
> "ARGF" means something like "flag argument", so to say it interprets
> the consecutive data as the flag argument depending on the context.
> The E-prefix just says that if that's not possible, it should nut just
> return NULL, but call a certain function (given in the argument) and
> then exit.
> 
> With best regards
> 
> Laslo
> 
> -- 
> Laslo Hunhold 
> 

Re: [dev] dl.suckless.org file integrity github project

[Aaron Toponce]

On Fri, Aug 25, 2017 at 08:12:12AM +0200, Anselm R Garbe wrote:
> - (optional) repo owners/maintainers should sign their future git tags
> for release creation by using their own private PGP key.

Optionally, for those who don't want to use OpenPGP, the author of libsodium
created Minisign back in 2015. It only signs and verifies, and does not do any
encryption or decryption, but it might be worth looking into for those who
don't want to rely on OpenPGP keys.

https://github.com/jedisct1/minisign

-- 
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o


signature.asc
Description: PGP signature

Re: [dev] dl.suckless.org file integrity github project

[Mattias Andrée]

On Fri, 25 Aug 2017 16:48:13 +0200
Anselm R Garbe  wrote:

> Hi Mattias,
> 
> On 25 August 2017 at 16:32, Mattias Andrée  wrote:
> > On Fri, 25 Aug 2017 13:54:41 +0200
> > Anselm R Garbe  wrote:
> >  
> >> On 25 August 2017 at 12:56, Laslo Hunhold  wrote:  
> >> > On Fri, 25 Aug 2017 08:12:12 +0200
> >> > Anselm R Garbe  wrote:  
> >> >> - (optional) repo owners/maintainers should sign their future git tags
> >> >> for release creation by using their own private PGP key.  
> >> >
> >> > the public PGP-keys could be put on the
> >> > http://suckless.org/people/*-pages.  
> >>
> >> Either that, or perhaps we can reinstate the old fashion of
> >> suckless.org/~user/ homedir.  
> >
> > Wouldn't it be best to have all keys in one page?  
> 
> Sure it would, probably best is dl.suckless.org as well.
> 
> My only concern with the wiki page is, that everybody could presumably
> tamper the pubkeys there, since we accept upstream wiki changes. Of
> course they need to be reviewed, but how do I know that Laslo's pubkey
> is really Laslo's pubkey without hassle when reviewing some public
> wiki change?
> 
> Hence my suggestion to put them into a URL position that requires ssh
> access for pushing onto suckless.org, which is given for
> maintainers/repo owners.
> 
> BR,
> Anselm

Each user could have a directory called pgp-keys and dl.suckless.org
could list those directories. This would allow us to store old keys
in a structured manner.

An alternative is that the owner of a repo commits his key to the
repo under /.pgp-keys.


pgpwCiVeIBYSN.pgp
Description: OpenPGP digital signature

Re: [dev] dl.suckless.org file integrity github project

[Mattias Andrée]

On Fri, 25 Aug 2017 13:54:41 +0200
Anselm R Garbe  wrote:

> On 25 August 2017 at 12:56, Laslo Hunhold  wrote:
> > On Fri, 25 Aug 2017 08:12:12 +0200
> > Anselm R Garbe  wrote:  
> >> - (optional) repo owners/maintainers should sign their future git tags
> >> for release creation by using their own private PGP key.  
> >
> > the public PGP-keys could be put on the
> > http://suckless.org/people/*-pages.  
> 
> Either that, or perhaps we can reinstate the old fashion of
> suckless.org/~user/ homedir.
> 
> BR,
> Anselm
> 

Wouldn't it be best to have all keys in one page?


pgp2rJBh8bHLi.pgp
Description: OpenPGP digital signature

Re: [dev] dl.suckless.org file integrity github project

[Anselm R Garbe]

On 25 August 2017 at 12:56, Laslo Hunhold  wrote:
> On Fri, 25 Aug 2017 08:12:12 +0200
> Anselm R Garbe  wrote:
>> - (optional) repo owners/maintainers should sign their future git tags
>> for release creation by using their own private PGP key.
>
> the public PGP-keys could be put on the
> http://suckless.org/people/*-pages.

Either that, or perhaps we can reinstate the old fashion of
suckless.org/~user/ homedir.

BR,
Anselm

Re: [dev] dl.suckless.org file integrity github project

[Laslo Hunhold]

On Fri, 25 Aug 2017 08:12:12 +0200
Anselm R Garbe  wrote:

Dear Anselm,

> - (optional) repo owners/maintainers should sign their future git tags
> for release creation by using their own private PGP key.

the public PGP-keys could be put on the
http://suckless.org/people/*-pages.

-- 
Laslo Hunhold 

Re: [dev] dl.suckless.org file integrity github project

[Nick]

Quoth Joshua Haase: 
> It's not so many work if git is configured to always sign and/or the
> package build system sign by default.

Configuring git to sign every commit is a pain if you have a 
passphrase on your gpg key, or it's tied to a smartcard; entering 
that every time you commit makes the process a lot more annoying.  
Yes, I'm sure you could configure gpg-agent to some mode to mitigate 
that somewhat, but I don't think it's worth it. Just for each tag 
would be fine.

Re: [dev] dl.suckless.org file integrity github project

[Anselm R Garbe]

Hi there,

let me summarise what we will carry out during the upcoming hackathon
besides a load of other stuff:

- (mandatory) introduction of HTTPS besides http support
- (mandatory) sorting the maintainership/ownership of suckless repos
(incl. the right to commit/accept/deny patch contributions)
- (mandatory) on release creation making sure that sha256 hashsums are
present for tarball verification on dl.suckless.org
- (optional) repo owners/maintainers should sign their future git tags
for release creation by using their own private PGP key.

BR,
Anselm

Re: [dev] dl.suckless.org file integrity github project

[hiro]

my grandmother also got all her pots stolen when she gave it to a
person promising to bless them against bad ghosts. pgp is just a more
modern version of that tale they told.

some are apparently using the pgp tale to associate their names to
random software projects. probably didn't manage to get the dish
washer job, this is their way in to google.