Thank you @ncopa, I appreciate your feedback and explanation. But the cute Psyko Alice closed it anyway. And I believe, that she would come with some other issue (like the mentioned mbedtls). I am just a lonely developer, who must find solutions not only for one platform. I like Alpine Linux, but I have also other tasks. Maybe I will come back one day.. or maybe someone else will take this unfinished piece of code from the dusty ground.
Sorry, but I also decided that I've wasted too much time here. I don't consider your mentors helpful enough. I accept your strict rules and wish you good luck.
And you will not accept this merge request without it?
Can you please explain it to me?
Is it a problem?
Oldes Huhuman (691ddfd9) at 06 May 07:02
testing/rebol-stage0: new aport
@ncopa Sorry, but I don't know, how to squash already pushed commits. So should I close this pull request and give it another try? But then someone asks for another change and I will be in the same situation:/ I would like to know, what activity is expected from me? And I am still only in the stage0 :/
Oldes Huhuman (34de7c5c) at 05 May 12:08
testing/rebol-stage0: removed unused code
... and 6227 more commits
Is this the right way to ping @team/mentors? What should I do?
Hi @kdaudt, I have !44734 (closed) and !44719 (closed) requests still in the review and now I received (probably automated) message on the second one, that it may be closed, because there is no activity. What kind of activity I must do to have any of these two (if I don't count this one) requests accepted?
Thank you very much!
Hi @team/mentors, what kind of activity do you expect? I actually wait for your activity to merge it or not. And if not exactly this one, then definitely this rebol-stage0
: !44734 (closed)
My main goal is to have a package for Rebol !44519 (closed), but it looks that it is not so easy to get thru your review process.
If I could use the above mentioned rebol-stage0
package, I could use it to build this Siskin builder package, which I could then use to build the Rebol package.
Hi @ptrcnull, is there something what I could do to move this forward? Thanks.
Oldes Huhuman (1ad666e7) at 14 Mar 19:20
testing/rebol-stage0: removed unused code
Oldes Huhuman (9f81f325) at 03 Mar 17:44
testing/rebol-stage0: not using hard-coded package version
... and 35 more commits
Oldes Huhuman (8c28e7e2) at 03 Mar 17:32
testing/rebol-stage0: not using hard-coded package version
I created the rebol-stage0
already !44734 (closed), but if I understand it well, I will have to wait until it is merged to use it elsewhere, am I right?
https://github.com/Oldes/Rebol3 Rebol version used to initially bootstrap itself
My siskin
is a universal tool, which may be used to build other projects, not just Rebol, without need to use anything else (except real compiler).
And yes, I am using a little bit older Rebol sources (where are included all pre-generated files) in a static archive, like you need. I use this temporary Rebol to build the first siskin
, which is actually customised Rebol, but not including all features, like no Repl console, but including all scripts written in Rebol, which does the job. Maybe this may help to understand it: https://github.com/Oldes/Rebol3/issues/60
Is it really so important for you, to have some -stage0 package, which would be used only to get the first version of something else? Because if there would be already available the siskin
package, I can use it to build a newer version of itself, to build fully featured rebol
or whatever else:/
Because to make some future version of my Siskin builder, I don't want to use some outdated Rebol, but Siskin builder itself.
I am really a little bit confused of this situation:/
Oldes Huhuman (d9fa725f) at 02 Mar 22:20
testing/siskin: using Rebol version 3.10.5
... and 5 more commits