WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: How are Tiny Core Extensions managed/source controlled?  (Read 1839 times)

Offline marcosscriven

  • Newbie
  • *
  • Posts: 1
How are Tiny Core Extensions managed/source controlled?
« on: June 23, 2015, 12:08:40 AM »
Hi

I was just looking to install OpenConnect which I was sure I'd seen when I initially searched Google for 'Tiny Core OpenConnect'.

Sure enough it's here: http://distro.ibiblio.org/tinycorelinux/3.x/tcz/. But to my disappointment, it's not in any subsequent versions.

From my experience I expected something along the lines of OpenWrt's opkg setup. Like TCE, it has packages here: https://downloads.openwrt.org/attitude_adjustment/12.09/x86/generic/packages/

But the difference seems to be that they also keep the build for each of these source controlled. Look at this one of OpenConnect: https://github.com/openwrt/packages/tree/master/net/openconnect. It doesn't mirror the source - it just records the config used, any patches, and a Makefile.

Does TCE have anything similar? Am I right that if I want to reinstate the OpenConnect, I'm essentially starting from square one?

Marcos


Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: How are Tiny Core Extensions managed/source controlled?
« Reply #1 on: June 23, 2015, 12:35:52 AM »
You can send the extension maintainer a pm and request an update for openconnect.

The extension build instructions/build script are normally posted at, for example:

http://www.tinycorelinux.net/6.x/x86/tcz/src/

..but in the case of openconnect, no build details were posted.