First port written - please feedback
Hi, I joined crux last week and now have created my first port. You can find it here: http://sebastian-bechtel.info/crux/ports/ Please give me some feedback whether I made everything right. One question I've got: Should I put an .httpup file on my webspace? It seems like portspage doesn't include an option for that. However, on the ports database on the crux website their is always such a link and I think it's very practical. Best regards, Sebastian
On 21.02.2013 0:27, me@sebastian-bechtel.info wrote:
Hi,
Hello!
I joined crux last week and now have created my first port.
Welcome.
You can find it here: http://sebastian-bechtel.info/crux/ports/
I get a 403 Forbidden so I cannot look at your port.
Please give me some feedback whether I made everything right.
First of all: check out prtverify from the prt-utils port. It can serve as a starting point for creating "nice" CRUX ports.
One question I've got: Should I put an .httpup file on my webspace? It seems like portspage doesn't include an option for that. However, on the ports database on the crux website their is always such a link and I think it's very practical.
If you think your ports are interesting/good enough to be listed on our ports page please consider http://crux.nu/portdb/?a=register for more details on the application process. Repositories are served via rsync or httpup. Until a successful application httpup is a nice/good to have but purely optional. Using rsync/httpup has the advantage that you can provide interested users with a convenient "link" like httpup sync http://www.mizrahi.com.ve/crux/pkgs/#anki anki to check your port(s) out. So this is up to you. with kind regards, Thomas
Zitat von Thomas Penteker <tek@serverop.de>:
On 21.02.2013 0:27, me@sebastian-bechtel.info wrote:
You can find it here: http://sebastian-bechtel.info/crux/ports/
I get a 403 Forbidden so I cannot look at your port.
Fixed it. I didn't add Options Indexes in the apache config.
Please give me some feedback whether I made everything right.
First of all: check out prtverify from the prt-utils port. It can serve as a starting point for creating "nice" CRUX ports.
Thanks, this tool is very helpful. I've got two errors. One was the wrong man directory, I fixed this. The second is usr/share/locale what should I do with it?
One question I've got: Should I put an .httpup file on my webspace? It seems like portspage doesn't include an option for that. However, on the ports database on the crux website their is always such a link and I think it's very practical.
If you think your ports are interesting/good enough to be listed on our ports page please consider http://crux.nu/portdb/?a=register for more details on the application process. Repositories are served via rsync or httpup.
I think I'll practise a bit before realeasing my ports into the wild ;)
with kind regards,
Thomas
Sebastian
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
On 21/02/13 at 11:23am, me@sebastian-bechtel.info wrote:
First of all: check out prtverify from the prt-utils port. It can serve as a starting point for creating "nice" CRUX ports.
Thanks, this tool is very helpful. I've got two errors. One was the wrong man directory, I fixed this. The second is usr/share/locale what should I do with it?
If there is no way to configure it without l10n, so just add rm -r $PKG/usr/share/locale to the end of your build function. -- Peter
participants (3)
-
me＠sebastian-bechtel.info -
Peter A. Shevtsov -
Thomas Penteker