Registration request + unregistration requests

 And on we go.

 I'd like to register the admin/s6-portable-utils package, with the
following command names:

s6-basename
s6-chmod
s6-chown
s6-clock
s6-cut
s6-dirname
s6-echo
s6-env
s6-expr
s6-false
s6-format-filter
s6-head
s6-ln
s6-maximumtime
s6-cat
s6-grep
s6-linkname
s6-ls
s6-mkdir
s6-mkfifo
s6-nice
s6-nuke
s6-pause
s6-printenv
s6-quote

Re: Registration request help

Registration request

 Hi,

 Maybe I'm the only one on Earth who still does this.

 But I'd like to register the admin/s6 package anyway,
and the following names in /command that it provides:

s6-ftrigrd
s6-ftrig-listen1
s6-ftrig-listen
s6-ftrig-notify
s6-ftrig-wait
s6-cleanfifodir
s6-mkfifodir
s6-svscan
s6-supervise
s6-svc
s6-svscanctl
s6-svok
s6-svstat
s6-svwait
s6-envdir
s6-envuidgid
s6-fghack
s6-log
s6-setlock
s6-setsid
s6-setuidgid
s6-softlimit
s6-tai64n
s6-tai64nlocal

 I wanted the "s4" name, but some open source software was released in
October 2010 by Yahoo and uses the name "S4", so - after much cursing -
I decided to avoid potential confusion and register "s6" instead.
 There's no conflict on "s6" as far as I can tell.

 s6 is a software suite that provides:
 - instant notification tools and libraries
 - process supervision tools (without any active waiting), including an
init replacement
 - hooks for higher-level service management.

--

-- 
 Laurent

on slashpackage hierarchy

re "Why classify packages at all? Why admin/daemontools instead of
simply daemontools? The answer is simply that many people complain
when a single directory gets too big. "

I used to classify by categories, my downloaded software (/setups) and
downloaded documentation (/setups/doc/), as well as my own work
documents (~/work/ - letters, legal documents for many people I have
assisted, and other work products).

Problem: Categories overlap (eg web, mail, net), often horribly (same eg.).

Problem: Newer created categories may be 'more appropriate' for a
package previously assigned to a different category.

Problem: Package management tools must first map from package name to
category name, before locating a named package (eg. user wants to show
"package-status djbdns").

1)
Underlying dynamic: human need for complexity management tools.

Categorization is a legitimate complexity management tool.

Alphabet single-letter directories is a legitimate complexity management tool.
 - Eg: Debian's pool/ package hierarchy
 - debian also use liba/, libb/ etc, since so many libs they messed up l/

I changed my /setups/*category* (setups = software downloads) and
/setups/doc/*category*, and /work/*category*, to be as follows:
/setups/[0-9a-z]/*
/setups/doc/[0-9a-z]/*
/work/[0-9a-z]/*

~/work example:
~/work/m/matter/[au|us|etc]/[a-z]/*

eg:
~/work/f/forms/*
~/work/m/matter/au/h/harkness-zenaan/*
~/work/m/matter/au/s/smith-john/*

In my case, country (au|us) is a category, and then the alphabetical
by surname. This works very well for me; makes it easy to locate a
particular client's work products.

Alphabetical directories are a desirable complexity management tool to
me, once I hit more than about 50 entries in a directory. Filesystem
navigation/ tab completion works well for me.

Since I'm on GNU system, I can and do use symlinks to add in
categories as well, as a convenience, in my /setups/ hierarchy.

If I were to use /package or similar, I would not use it without this
debian-style alphabetical directories complexity management tool. I
would have:
/package/a/*
/package/b/*
etc

If you included such a recommendation in your slashpackage docs, I
might use /package. If you recommended against doing so, I would use a
different /apps directory. An alphabetical organization does not
conflict with your categorization organization.
Alphabetical means 26 extra directories inside /package (or eg /apps).

Alphabetical means low cognitive overhead. I know default installed
djbdns can be found at:
 /package/d/djbdns/*

This is desirable not only for humans, but also for automated tools/
package management tools. Eg debian's
 - "apt-cache show djbdns"
would not have to first map from package name to category name, just
to find the package, but can instead just go to /package/d/...

(I imagine /package/d/unversioned-name/META/ might be a good standard
for metadata location; but that's another conversation/ process.)

Feedback sought,
Zenaan

Registration request

 Dan, are you still maintaining the /command and /package registry?

 If you are, I'd like to register the following additional /command
names for the admin/execline package:

 ifelse
 multidefine
 forx
 forbacktickx
 loopwhilex

 No name conflicts AFAIK.

 I'd also like to relinquish all name claims associated to the
admin/pipe-tools and net/minssl packages. admin/pipe-tools is obsolete
and will soon be replaced with a completely different package;
net/minssl will never come out because of cryptography restriction laws.

 Thank you,

--

-- 
 Laurent

Registration request

 Hi,
 I would like to register the name

 /command/tryexec

 for the admin/execline package.
 No name conflicts as far as I know.
 Thank you,

--

-- 
 Laurent

registration request

new package: net/tuntools
description: tools for working with virtual network interfaces
future URL: <URL:http://code.dogmap.org./tuntools/>
commands: tun-io, tun-open, tun-start

package: misc/fdtools
new commands: multitee, pipecycle

I.e., I'm volunteering to take over maintainership of multitee from
http://cr.yp.to/software/multitee-3.0.shar.gz, preserving the
interface (except possibly changing some error exit codes).
Otherwise, no name conflicts AFAIK.

paul

Request: add command to mail/getmail package

Existing package: mail/getmail
Existing commands: getmail getmail_maildir getmail_mbox 

New command:     getmail_fetch

Thanks,

Charles
--

-- 
-----------------------------------------------------------------------
Charles Cazabon                          <package <at> discworld.dyndns.org>
GPL'ed software available at:               http://pyropus.ca/software/
-----------------------------------------------------------------------

daemontools installation problem

Compiler warnings when compiling daemontools (like: warning: passing arg 2 of `getgroups' from incompatible pointer type)

Hi

I'm receiving these compiler warnings when installing the package.

Note that I did only the compile part to not disrupt my system.

I have already applied the error.h patch, or it wouldn't compile at all.

Has anyone got any good ideas? Do you get the same?

Systype are: linux-2.6.3-7mdk-:i386-:-:genuineintel-00000f34-bfebfbff-:-

Best regards

HC

[root <at> server daemontools-0.76]# package/compile
Linking ./src/* into ./compile...
Compiling everything in ./compile...
./compile byte_chr.c
./compile byte_copy.c
./compile byte_cr.c
./compile byte_diff.c
./compile byte_rchr.c
./compile fmt_uint.c
./compile fmt_uint0.c
./compile fmt_ulong.c
./compile scan_ulong.c
./compile str_chr.c
./compile str_diff.c
./compile str_len.c
./compile str_start.c
./makelib byte.a byte_chr.o byte_copy.o byte_cr.o byte_diff.o \
byte_rchr.o fmt_uint.o fmt_uint0.o fmt_ulong.o scan_ulong.o str_chr.o \
str_diff.o str_len.o str_start.o
./compile envdir.c
./compile alloc.c
./compile alloc_re.c
./compile buffer.c
./compile buffer_0.c
./compile buffer_1.c
./compile buffer_2.c
./compile buffer_get.c
./compile buffer_put.c
./compile buffer_read.c
./compile buffer_write.c
./compile coe.c
./compile env.c
./compile error.c
./compile error_str.c
./compile fd_copy.c
./compile fd_move.c
./compile fifo.c
./compile lock_ex.c
./compile lock_exnb.c
./compile ndelay_off.c
./compile ndelay_on.c
./compile open_append.c
./compile open_read.c
./compile open_trunc.c
./compile open_write.c
./compile openreadclose.c
./compile pathexec_env.c
./compile pathexec_run.c
pathexec_run.c: In function `pathexec_run':
pathexec_run.c:18: warning: implicit declaration of function `execve'
./compile chkshsgr.c
chkshsgr.c: In function `main':
chkshsgr.c:10: warning: passing arg 2 of `getgroups' from incompatible
pointer type
chkshsgr.c:10: warning: implicit declaration of function `setgroups'
./load chkshsgr
./chkshsgr || ( cat warn-shsgr; exit 1 )
./choose clr tryshsgr hasshsgr.h1 hasshsgr.h2 > hasshsgr.h
./compile prot.c
prot.c: In function `prot_gid':
prot.c:13: warning: implicit declaration of function `setgroups'
prot.c:15: warning: implicit declaration of function `setgid'
prot.c: In function `prot_uid':
prot.c:20: warning: implicit declaration of function `setuid'
./compile readclose.c
./compile seek_set.c
seek_set.c: In function `seek_set':
seek_set.c:9: warning: implicit declaration of function `lseek'
./compile sgetopt.c
./compile sig.c
./compile sig_block.c
./compile sig_catch.c
./compile sig_pause.c
./compile stralloc_cat.c
./compile stralloc_catb.c
./compile stralloc_cats.c
./compile stralloc_eady.c
./compile stralloc_opyb.c
./compile stralloc_opys.c
./compile stralloc_pend.c
./compile strerr_die.c
./compile strerr_sys.c
./compile subgetopt.c
./compile wait_nohang.c
./compile wait_pid.c
./makelib unix.a alloc.o alloc_re.o buffer.o buffer_0.o buffer_1.o \
buffer_2.o buffer_get.o buffer_put.o buffer_read.o buffer_write.o \
coe.o env.o error.o error_str.o fd_copy.o fd_move.o fifo.o lock_ex.o \
lock_exnb.o ndelay_off.o ndelay_on.o open_append.o open_read.o \
open_trunc.o open_write.o openreadclose.o pathexec_env.o \
pathexec_run.o prot.o readclose.o seek_set.o sgetopt.o sig.o \
sig_block.o sig_catch.o sig_pause.o stralloc_cat.o stralloc_catb.o \
stralloc_cats.o stralloc_eady.o stralloc_opyb.o stralloc_opys.o \
stralloc_pend.o strerr_die.o strerr_sys.o subgetopt.o wait_nohang.o \
wait_pid.o
./load envdir unix.a byte.a
./compile envuidgid.c
./load envuidgid unix.a byte.a
./compile fghack.c
./load fghack unix.a byte.a
./compile match.c
./compile matchtest.c
matchtest.c: In function `main':
matchtest.c:22: warning: implicit declaration of function `_exit'
./load matchtest match.o unix.a byte.a
./compile deepsleep.c
./compile multilog.c
multilog.c: In function `startprocessor':
multilog.c:200: warning: passing arg 2 of `execve' from incompatible pointer
type
multilog.c: In function `fullcurrent':
multilog.c:216: warning: implicit declaration of function `rename'
./compile iopause.c
./compile tai_now.c
./compile tai_pack.c
./compile tai_sub.c
./compile tai_unpack.c
./compile taia_add.c
./compile taia_approx.c
./compile taia_frac.c
./compile taia_less.c
./compile taia_now.c
./compile taia_pack.c
./compile taia_sub.c
./compile taia_uint.c
./makelib time.a iopause.o tai_now.o tai_pack.o tai_sub.o \
tai_unpack.o taia_add.o taia_approx.o taia_frac.o taia_less.o \
taia_now.o taia_pack.o taia_sub.o taia_uint.o
./compile timestamp.c
./load multilog deepsleep.o timestamp.o match.o time.a unix.a byte.a
./compile pgrphack.c
./load pgrphack unix.a byte.a
./compile readproctitle.c
./load readproctitle unix.a byte.a
./compile setlock.c
./load setlock unix.a byte.a
./compile setuidgid.c
./load setuidgid unix.a byte.a
./compile softlimit.c
./load softlimit unix.a byte.a
./compile supervise.c
supervise.c: In function `announce':
supervise.c:78: warning: implicit declaration of function `rename'
supervise.c: In function `trystart':
supervise.c:102: warning: passing arg 2 of `execve' from incompatible
pointer type
./load supervise deepsleep.o time.a unix.a byte.a
./compile svc.c
./load svc unix.a byte.a
./compile svok.c
./load svok unix.a byte.a
./compile svscan.c
svscan.c: In function `start':
svscan.c:104: warning: passing arg 3 of `pathexec_run' from incompatible
pointer type
svscan.c:123: warning: passing arg 3 of `pathexec_run' from incompatible
pointer type
./load svscan unix.a byte.a
./compile svstat.c
./load svstat time.a unix.a byte.a
./compile tai64n.c
./load tai64n timestamp.o time.a unix.a byte.a
./compile tai64nlocal.c
./load tai64nlocal unix.a byte.a
env - /bin/sh rts.tests 2>&1 | cat -v > rts
rm -f sysdeps
cat systype compile load >> sysdeps
grep sysdep direntry.h >> sysdeps
grep sysdep haswaitp.h >> sysdeps
grep sysdep hassgact.h >> sysdeps
grep sysdep hassgprm.h >> sysdeps
grep sysdep select.h >> sysdeps
grep sysdep uint64.h >> sysdeps
grep sysdep iopause.h >> sysdeps
grep sysdep hasmkffo.h >> sysdeps
grep sysdep hasflock.h >> sysdeps
grep sysdep hasshsgr.h >> sysdeps
Copying commands into ./command...

Re: Registration of the dcachesh and dcachereplay tools

I hereby want to register
  dcachesh
  dcachereplay
as parts of the data/dcache package.

Regards, Uwe