Changes between Version 2 and Version 3 of WritingBepFile
- Timestamp:
- 01/20/13 00:11:00 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WritingBepFile
v2 v3 1 = Writing !BepFile = 2 1 3 This article gives basic overview of writing a .bep file for haikuporter. Prior to reading it, you are advised to read BepFile article. This entry assumes that you have read and understood it. 2 4 3 == BepFile name ==5 == !BepFile name == 4 6 5 BepFile should be named as "Program name"-"Program version".bep format, e.g. `transmission-2.75.bep`, `curl-7.28.1.bep`. Also some additional information can be added to the filename. An example of that case is `libsdl-2.0-hg-cmake.bep` file. From it's name we can notice that version to be built with cmake is going to be downloaded from sdl's mercurial server.7 !BepFile should be named as "Program name"-"Program version".bep format, e.g. `transmission-2.75.bep`, `curl-7.28.1.bep`. Also some additional information can be added to the filename. An example of that case is `libsdl-2.0-hg-cmake.bep` file. From it's name we can notice that version to be built with cmake is going to be downloaded from sdl's mercurial server. 6 8 7 9 == How HaikuPorter works == … … 11 13 * Process the arguments passed 12 14 * Search for the specified package in ports tree 13 * Read data from BepFile15 * Read data from !BepFile 14 16 * If port is not stable, then warn the user 15 17 * Print the `MESSAGE` string from the bep … … 17 19 * Warn user about the port dependencies 18 20 * Download the sources 19 * Check that downloaded file's checksum matches with the one specified in the `CHECKSUM_MD5` field of the BepFile (if it is not empty)21 * Check that downloaded file's checksum matches with the one specified in the `CHECKSUM_MD5` field of the !BepFile (if it is not empty) 20 22 * Unpack sources to the work directory 21 23 * Patch sources (*) … … 28 30 Items marked with (*) are controlled by the commandline arguments, default behaviour is to patch and build. 29 31 30 == Writing BepFile ==32 == Writing !BepFile == 31 33 32 34 0. Read porting Guidelines … … 41 43 a. If it fails, find the reason why and fix it 42 44 b. [#Patchfile Make a patch] 43 7. Write `BUILD` section of your BepFile reflecting the steps you have made45 7. Write `BUILD` section of your !BepFile reflecting the steps you have made 44 46 * Don't forget that by default the `BUILD` script is launched from the work directory, so you possibly need to cd in the beginning 45 47 8. Write `INSTALL` section 46 * When adding paths to the BepFile, don't hardcode them. Use [wiki:FindDirectory finddir] instead48 * When adding paths to the !BepFile, don't hardcode them. Use [wiki:FindDirectory finddir] instead 47 49 9. If program has tests, write `TEST` section 48 50 10. Add miscellaneous info … … 56 58 == License file == 57 59 58 If project you are porting has license that hasn't been added yet to the haiku's default list of licenses, make a text file with the name of this license containing it's text and add it to the license folder in BepFile's dir ([http://ports.haiku-files.org/browser//haikuports/trunk/app-misc/figlet example]).60 If project you are porting has license that hasn't been added yet to the haiku's default list of licenses, make a text file with the name of this license containing it's text and add it to the license folder in !BepFile's dir ([http://ports.haiku-files.org/browser//haikuports/trunk/app-misc/figlet example]). 59 61 60 62 == Patch file ==
