-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🔮 ldoc-custom binary origin #1
Comments
This is the origin of those scripts. My bad, open source should show everything. It's just an 'ldoc' wrapper with some scripts that help you replace the CSS file and add a little JS to the HTML file to fix 'the a tag with name properties not working already'. I really don't know why?? |
Great, thanks for your prompt reply, yes I'm sure you can imagine how bad it looks to put a binary with no indication of how it was built, I suggest to include in the same repo to avoid confusions? I'm sure I wasn't the only one who saw this and avoided your solution, I'm just the first who report it. Thanks again 🙏 |
umm I still cant figure how this produced a binary.. for a wrapper as you describe I expected something like this; #!/bin/bash
echo doing_stuff_stuff
echo more_stuff..
ldoc $@ wont be a binary, am I missing something? |
ah sorry, This is the origin |
no worries, thanks, but that still wont be a binary right? $ file ldoc-custom
ldoc-custom: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=d13794c3e9e3393d0508bf4be6ef846e780a7185, for GNU/Linux 4.4.0, stripped the file you linked is; $ file scripts/stilux/users/ldoc-custom
scripts/stilux/users/ldoc-custom: Bourne-Again shell script, Unicode text, UTF-8 text executable |
I updated ldoc-custom new. May be this is not good. I wrote it quite a while ago. |
I see you replaced the binary on 6290da2 Now I cant stop wondering what it was all the while before your commit! 😅 |
I don't see the source for this binary
ldoc-custom
How did this came to be?
What is it exactly?!
The text was updated successfully, but these errors were encountered: