[quote="dlang, post:33, topic:123, full:true"]The download mechanism should ensure that the download is complete (and everything except ftp does this today)
David Lang
[/quote]opkg (package manager in LEDE) checks package checksum (Chaos Calmer uses MD5, LEDE trunk uses SHA256), as you can't rely on the network stack alone.
[quote="tmomas, post:29, topic:123, full:true"]You can now upload + delete files in /pkgdata/
[/quote]Hmm, closer but still nope. I created a dummy start page to get the namespace to show up https://wiki.lede-project.org/pkgdata/start
But it seems I cannot upload plain text files, it fails with "Upload denied. This file extension is forbidden!"
I tried uploading pdf files (actually a renamed text file) and it works (but of course it's then treated like a file, not as wiki pages)
It does not seem to like text files without extension, nor text files with .txt extension.
I think this needs some tweaking again, btw, for me isn't an issue to rename all files with a specific extension. 
Try again, I allowed txt upload now.
Please let me know when you are finished, since this possibility must not exist longer than needed.
Only now I realized that there are some multiselects, which need to be changed slightly:
Categories_pkg-category -> Categories_pkg-categorys
Architectures_pkg-arch -> Architectures_pkg-archs
LEDE releases_lede-release -> LEDE releases_lede-releases
Obviously without the ** marking.
Sidenote1: That's one more strange thing about this forum editor: You can not format substrings (e.g. bold).
Substring -> the part between the ** should be bold, but it isn't (at least in the preview).
Yes, S ubstr ing works, but is looking odd.
Sidenote2: The reason for the dataentry update I ran this morning was exactly this: I forgot to add an 's' at the end of "Flash MB", which lead to this field showing up only as dropdown, not a multiselect. D'oh! 
...and if you want to show up "Bug report" as link, then you need to name it "Bug report_url"
Try putting two backticks before the first ** as workaround:
sub``**sub**string = sub``substring
You are certainly going to write that down somewhere, so others can look it up later? 
ok, will do the changes.
Please let me know when you are finished, since this possibility must not exist longer than needed.
I need to be able to test a few things for a few weeks or so at most, then I was hoping you could simply set the server to run the script every X days or so (it's using only the basic tools like wget/awk/sed/bash/wc, that should be installed already in most servers).
No problem to have this status for several weeks. We just must not forget to to disallow txt again after the tryout period.
Hm, btw, the LEDE releases_lede-release field should be left single as packages from trunk or older releases are different (different version/size for sure, maybe dependencies or mantainer too or whatever else may be different apart from the name), so they should have separate entries.
Since the name is the same it should link to the same package page though, correct?
As you like... if the package name contains also the version -> Name_pkg-page will link to a separate page for each version.
'Name: Package V1' -> links to 'package_v1'
'Name: Package V2' -> links to 'package_v2'
...
...and make that "Dependencies_pkg-pages" please. This way, dependencies will show up also as wiki pagelinks.
I prepared a packages page which contains all fields available for a package.
https://wiki.lede-project.org/packages/start
If you create the txt files correctly, they will show up automatically in this table. Magic! 
To see how the txt files are expected: https://wiki.lede-project.org/pkgdata/testpackage?do=edit
Ok, rebuilding.
Another question, would it be possible to disable edits to some/all package fields? My idea was that this system would fill them automatically by reading package lists and sources, and that any user edit should be directed to the package page (or sources).
Currently I need the edit interface enabled as I need to test things though, so don't turn it off now. 
...and make that "File size_pkg-filesize". This way, the kB gets added automatically.
Enter "23" -> will show up later as 23kB
The dataentry pages can be write protected, but only the whole page, not single datafields.
BTW: If you make it [quote="tmomas, post:37, topic:123"]
Maintainer_pkg-maintainer : |$package_maintainer
[/quote]
then the maintainer name will link to /contact
Mind the pipe in front of $package_maintainer.
sigh, I uploaded a batch of files and the media manager interface shows them correctly, problem is, they don't seem to show in the Site Map, nor in the table.
I think the wiki is placing them in a dedicated folder for uploaded things, not in the /pkgdata folder.
Waaaaah, the wiki is frustrating me. 
Will upload a zip for you to load them sometime in the future.
D'oh!
Sorry, I didn't think of the media manager uploading everything to the /media directory 
I moved the dataentries now to the correct location in /pkgdata.
Observations:
[quote="tmomas, post:49, topic:123, full:true"]Sorry, I didn't think of the media manager uploading everything to the /media directory [/quote]On the bright side, you can leave txt or whatever other extension enabled in the long term too.
On the dark side, you will need to move packages manually around a few times while I'm testing.
[quote] - Categories: Need to be separated by ','
[quote]- Maintainer: If you put a '|' (pipe) in front of the name, the name will automatically link to /contact[/quote]Not sure about how useful that would be, the recommended way to contact the mantainer is to open an issue/bugreport ticket anyway.
[quote]- LEDE release: Should we call it "snapshot" instead of "trunk"? This would fit better to https://downloads.lede-project.org/snapshots/ [/quote]I'd say no. That is trunk, built as snapshots daily or something.
Btw, I've found a way to shorten links. you must use the _wiki tag in the field name, then you can use wiki syntax to make the links as normal (also any other wiki syntax will work). They say here to not abuse this as it has a performance impact.
my test in the wiki here
EDIT: hmm, no it seems to show the text anyway in the table.
EDIT2: yes, it should work but you need to define that field as _wiki in the table too https://www.dokuwiki.org/plugin:struct:type_wiki
Just tested this with 6in4 entry, it shows as short link in the wiki too.
EDIT3: it seems I managed to screw up the database somehow, now there is a broken 6in4 entry I can't delete (I deleted the 6in4 entry text file and also tried to re-create the table, the borked entry persists). 
[quote="bobafetthotmail, post:50, topic:123"]
Should we call it "snapshot" instead of "trunk"? This would fit better to https://downloads.lede-project.org/snapshots/
I'd say no. That is trunk, built as snapshots daily or something.
[/quote]Well, to add some confusion to the discussion, "trunk" was actually main branch in the old SVN system, while now there is the "master" in git. Right now all old-timers still understand "trunk", but after a while it may start sounding weird.
A couple of comments to that table. You might need to adjust table column widths. Right now some look strange. E,g,
Adjust Luci to display max. 26 characters (= luci's own version string).
Longer version strings are cut to: "first 21c" + ".." + "last 3c"
The last 3 chars are used to preserve the possible PKG_REVISION string.
E.g. 'opkg' has only hash+PKG_REVISION, so using only start of the string
might not be optimal.
.
Ok, thanks for the clarification.
I think a better/modern naming would be "Nightly" then, as it is what most other projects use for similar "built-from-latest-est-est-development-sources-built-daily" releases.
This trunk-> Nightlies change should happen everywhere for consistency, but afaik that's only wiki or LEDE main site, so we can alter that fine.