Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: rmrichesjr on January 10, 2012, 04:47:04 PM
-
Where is the source for libssl-0.9.8? (It's a dependency of lighttpd, including the specific version number.) I looked in the following places, but it's not there--at least not by that name:
http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/src/ (http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/src/)
http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/ (http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/)
http://distro.ibiblio.org/tinycorelinux/2.x/tcz/src/ (http://distro.ibiblio.org/tinycorelinux/2.x/tcz/src/)
http://distro.ibiblio.org/tinycorelinux/tcz/src/ (http://distro.ibiblio.org/tinycorelinux/tcz/src/)
Are there other places I should be looking for source?
If the source is listed under a different name, is there a general algorithm that can find the source for a particular extension name? (I'm doing an embedded project using Tiny Core Linux as a base, and I'm trying to automate the process of downloading a small number of extensions. ... to reduce wear and tear on the
mouse, of course.)
Thank you,
Robert
-
http://www.openssl.org/source/ (http://www.openssl.org/source/)
Algorithm is easy: read .tcz package info file.
-
That's the upstream source. I'm looking for the exact source used in Tiny Core, including any patches and the build script. The project I'm working on requires exact sources used to build the binary packages in order to meet open source obligations.
-
There are no patches or build scripts. If you want to provide sources just take the ones from openssl.org like bmarkus said. If you want me to download and send you the file per mail just send me a pm.
-
Thanks.
-
Where is the source for libssl-0.9.8?
....
Are there other places I should be looking for source?
...
How about: http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/openssl-0.9.8 (http://distro.ibiblio.org/tinycorelinux/3.x/tcz/src/openssl-0.9.8)
This directory contains: 'openssl-0.9.8r.tar.xz' which according to the entry in the respective info file (i.e. "Current: 2011/06/20 Updated to 0.9.8r") looks to me to be the right file.
Now, the TC 4.x repo essentially contains just a copy of the extension from the TC 3.x repo. That might explain why there is no separate 'openssl-0.9.8' directory to be found in: http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/src/ (http://distro.ibiblio.org/tinycorelinux/4.x/x86/tcz/src/)
EDIT: Update of the last paragraph as gerald_clark correctly pointed out my mistake. This was just timely reminder that I my local mirror needs to be "relieved" of those extension files that meanwhile have been removed from the official repository.
-
4.x does not provide openssl-0.9.8
-
Thanks for the pointer to the openssl-0.9.8 source. In hindsight, I realize I could read the .info file and do a bit of deduction, but with there not being an openssl-0.9.8 binary extension in 4.x, I had ruled out that avenue.
Is there a general algorithm that can translate from the binary extension name (libssl-0.9.8 in this case) to the name of the source (openssl-0.9.8 in this case)?
I would think it would be helpful if perhaps a line could be added to the info file for cases like this where the names differ--something like this:
Source-name: openssl-0.9.8
It appears lighttpd-nodeps is another case where the source has a different name from the binary extension.