WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: build-dep aka buildscript  (Read 1475 times)

Offline caminati

  • Full Member
  • ***
  • Posts: 184
    • Homepage
build-dep aka buildscript
« on: February 04, 2011, 03:30:25 AM »
From http://wiki.tinycorelinux.com/Creating+Extensions:

Quote
It is not required, but certainly recommended, that you include any additional build instructions in a plain text file for future reference, mentioning such things as which extensions are required to build the package and what compile flags were used. This can be done in a file named "build-dep".

I wholeheartedly agree with the policy of creating an as detailed-as-possible build script when piling up an extension (slax preached the same in its guidelines, though almost nobody complied, whereas I love Slackware for its loyalty to this precept).
So in my only tcz submission I attached a build-dep/buildscript.

The question is: where did it go? What is the sense in recommending including a build script if, after submission, it is not accessible by the public? Or am I missing something?


Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10992
Re: build-dep aka buildscript
« Reply #1 on: February 04, 2011, 05:56:59 AM »
3.x/tcz/src/$PACKAGE on any mirror.
The only barriers that can stop you are the ones you create yourself.

Offline caminati

  • Full Member
  • ***
  • Posts: 184
    • Homepage
Re: build-dep aka buildscript
« Reply #2 on: February 04, 2011, 06:04:35 AM »
Silly me. Thanks!