WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Why only .core extensions in /opt/tce  (Read 2126 times)

Offline helander

  • Full Member
  • ***
  • Posts: 183
Why only .core extensions in /opt/tce
« on: August 15, 2009, 12:38:16 AM »
In order to create a remaster by adding extensions to /opt/tce, these extensions must apply to the .core naming scheme. WHY?

What is the reason for just allowing .core named extensions?

This means I have to rename all extensions I would like to put into my remaster.
What I have not explored, is if appbrowser's dependency function equals extensions with and without .core in the name. If not, having to rename the extensions to put them into /opt/tce, would break the extension dependency mechanism in the system.

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Why only .core extensions in /opt/tce
« Reply #1 on: August 16, 2009, 01:32:02 PM »
Queued in my todo. However remastering has not been the focal point of the development.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Why only .core extensions in /opt/tce
« Reply #2 on: August 17, 2009, 02:36:43 PM »
Completed. Will be in next 2.3RC2.
10+ Years Contributing to Linux Open Source Projects.