urlencode_build script

[mocore]

makefile for building gridsite urlencode 
* modified/updated version of https://github.com/2ion/urlencode

Code: [Select]

URL="http://raw.githubusercontent.com/CESNET/gridsite/gridsite-core_branch_2_0_5_cherry"
urlencode: get-source
gcc -02 -i ./interface src/urlencode.c src/grst_http.c -o urlencode

get-source:
install -m 0700 -d src
wget -Psrc $(URL)/src/urlencode.c
wget -Psrc $(URL)/src/grst_http.c
install -m 0700 -d interface
wget -Pinterface $(URL)/interface.c

clean:
-rm -rf src interface
-rm urlencode

build-deps
---
openssl-dev
linux- ${KERNEL} _api_headers.tcz
---

[gerald_clark]

And your question?

[mocore]

I was just posting the make file and build deps , so i dont forget/loose the info and just in case it was of any use/intrest to any one !

 I hope that is  no problem...  ( it should work but might have errors as it was a made by hand copy , idk if tab's will survive  )
I might get round to building a tcz and submiting it at some point , just not this one!

[gerald_clark]

Blogging is not allowed.
The script accomplishes nothing useful for Core.

[mocore]

Blogging is not allowed.
The script accomplishes nothing useful for Core.

It lets me build some bin i was missing in core ,
 any way the above had some errors so ..
 
This (hopfuly more useful) make script builds a tcz +  tcz.lst  and tcz.md5.txt 4core

Code: [Select]

URL="http://raw.githubusercontent.com/CESNET/gridsite/gridsite-core_branch_2_0_5_cherry"

mk-tcz: urlencode
mkdir -p /tmp/urlencode/usr/local/bin
cp ./urlencode /tmp/urlencode/usr/local/bin
mksquashfs urlencode urlencode.tcz
find /tmp/urlencode -not -type d   | cut -b 15- > urlencode.tcz.list
md5sum urlencode.tcz > urlencode.tcz.md5.txt

urlencode: get-source
gcc -O2 -I ./interface src/urlencode.c src/grst_http.c -o urlencode

get-source:
install -m 0700 -d src
[ -f ./src/urlencode.c ] || wget -Psrc $(URL)/src/urlencode.c
[ -f ./src/grst_http.c ] || wget -Psrc $(URL)/src/grst_http.c
install -m 0700 -d interface
[ -f ./interface/gridsite.h ] || wget -Pinterface $(URL)/interface/gridsite.h

clean:
-rm -rf  /tmp/urlencode
-rm urlencode urlencode.tcz urlencode.tcz.list urlencode.tcz.md5.txt
# -rm -rf src interface

Question's
Will the buildscripts/tree/  ever contain any scripts ?
Could  this script  'usefull' enough to be included in it?

[gerald_clark]

Yes, building and submitting the tcz is the proper thing to do.
The build scripts are submitted with the tcz as described in the wiki.
They are not posted in the forum.

[mocore]

Yes, building and submitting the tcz is the proper thing to do.
The build scripts are submitted with the tcz as described in the wiki.
They are not posted in the forum.

why not ? ... (and is this policy stated any where other than this post?)

relevant : https://forum.tinycorelinux.net/index.php/topic,27320.msg175869.html#msg175869

reiterating:

Question's
Will the buildscripts/tree/  ever contain any scripts ?

& wrt the above (now dead link to ) buildscripts/tree/
---
from : How to know which extension version is installed?

There is no historical archive of versions/md5sums anywhere, so it's not possible to know how many versions were skipped. edit: or to download a certain old extension version.

...

Thank you for your answers.
That's definitively a big issue of the extension system. I hope it will be fixed in a latter release.
Downloading the info file is only a dirty workaround because:
* there is no way to download both the tcz and the info file in a single "transaction" (that means that the info file can change while we are downloading the tcz file)
* the info file is only for information purpose and does not really encode a clear, unique and consistent version number (different versions of the same tcz are often uploaded with the same info file)

Another big flaw of the way extensions are managed in TinyCore is that there is no clear link to the source code that was compiled to produce the tcz binary, so it is not possible to recompile the extensions from sources by ourself, or check that no backdoor was introduced in the extension. For example, I provided the openjdk-8 extensions, and nobody asked me for the source code! It amazed me, because I read an article from the original author of TinyCore saying that extensions were always built from sources and that no binary extension without source code was allowed: that's simply untrue.

I am concerned of the security implications of all these points.

---

[Rich]

Hi mocore

Yes, building and submitting the tcz is the proper thing to do.
The build scripts are submitted with the tcz as described in the wiki.
They are not posted in the forum.

...

I'm presuming that last sentence was referring to both tczs and build scripts.

Extensions (tczs) belong in a centralized location (repo) where they can easily
be found, not scattered throughout the forum as attachments.

Build scripts belong under  VERSION/ARCH/tcz/src/ExtensionName/  for the
same reason listed above.

... why not ? ... (and is this policy stated any where other than this post?) ...

We are not lawyers, so not all policies are carved in stone.

We also don't have a written policy against using attachments as storage space for your computer.
That doesn't mean it's OK and will be tolerated.

... why not ? ... (and is this policy stated any where other than this post?) ...

As far as extensions are concerned, here:

2. No attachments/links of binary extensions

Although it's not stated, we do allow links to our own repositories.