APKBUILD examples:Haskell - Revision history

Orson Teodoro: Add category

2018-02-19T21:21:04Z

Add category

← Older revision		Revision as of 21:21, 19 February 2018
Line 47:		Line 47:

	You can also search on GitHub but this guide doesn't tell you how to integrate a GitHub Haskell project with a Cabal sandbox yet.		You can also search on GitHub but this guide doesn't tell you how to integrate a GitHub Haskell project with a Cabal sandbox yet.

			[[Category:Development]]

Orson Teodoro: Add section for where to find haskell packages

2018-02-07T00:56:24Z

Add section for where to find haskell packages

← Older revision		Revision as of 00:56, 7 February 2018
Line 1:		Line 1:
	'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python2-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called ~~cabal~~ which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.		'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python2-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called Cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.

	It is not necessary to create a separate package for a Haskell library with this method.		It is not necessary to create a separate package for a Haskell library with this method.
Line 41:		Line 41:

	As with licensing, make sure you put the licenses of the dependencies that cabal pulls also in the license= field.		As with licensing, make sure you put the licenses of the dependencies that cabal pulls also in the license= field.

			== Finding packages ==

			If you are a package creator, you can find additional packages in the [https://hackage.haskell.org/ Hackage] package archive.

			You can also search on GitHub but this guide doesn't tell you how to integrate a GitHub Haskell project with a Cabal sandbox yet.

Orson Teodoro: making a note about not needing separate package for a library.

2018-02-07T00:16:31Z

making a note about not needing separate package for a library.

← Older revision		Revision as of 00:16, 7 February 2018
Line 1:		Line 1:
	'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python2-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.		'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python2-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.

			It is not necessary to create a separate package for a Haskell library with this method.

	At this time, there is no site directory where all Haskell programs should go.		At this time, there is no site directory where all Haskell programs should go.

Orson Teodoro: mention licenses of dependencies

2018-02-06T23:35:19Z

mention licenses of dependencies

← Older revision		Revision as of 23:35, 6 February 2018
Line 37:		Line 37:
	}		}
	</pre>		</pre>

			As with licensing, make sure you put the licenses of the dependencies that cabal pulls also in the license= field.

Orson Teodoro: add --enable-relocatable

2018-02-06T23:28:06Z

add --enable-relocatable

← Older revision		Revision as of 23:28, 6 February 2018
Line 19:		Line 19:
	build() {		build() {
	# the cabal install will automatically fetch all dependencies and compile all dependencies and the main program		# the cabal install will automatically fetch all dependencies and compile all dependencies and the main program
	cabal install $pkgname-$pkgver		cabal install $pkgname-$pkgver --enable-relocatable
	}		}

Orson Teodoro: put variable in quotes and remove duplicate word

2018-02-06T23:23:55Z

put variable in quotes and remove duplicate word

← Older revision		Revision as of 23:23, 6 February 2018
Line 22:		Line 22:
	}		}

	After <code>cabal install</code> is done, it will place all the files in a hidden folder at <code>$builddir/.cabal</code>. Dump the contents of that folder into <code>"$pkgdir"/usr/lib/$pkgname</code>. Then, ~~then~~ make a symlink from $pkgname/usr/lib/$pkgname/bin/$pkgname to /usr/bin/$pkgname		After <code>cabal install</code> is done, it will place all the files in a hidden folder at <code>"$builddir"/.cabal</code>. Dump the contents of that folder into <code>"$pkgdir"/usr/lib/$pkgname</code>. Then, make a symlink from $pkgname/usr/lib/$pkgname/bin/$pkgname to /usr/bin/$pkgname

	Your package() statement should look like:		Your package() statement should look like:

Orson Teodoro: fix python version

2018-02-06T23:09:07Z

fix python version

← Older revision		Revision as of 23:09, 6 February 2018
Line 1:		Line 1:
	'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and ~~python4~~-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.		'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python2-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.

	At this time, there is no site directory where all Haskell programs should go.		At this time, there is no site directory where all Haskell programs should go.

Orson Teodoro: fix package()

2018-02-06T23:06:16Z

fix package()

← Older revision		Revision as of 23:06, 6 February 2018
Line 28:		Line 28:
	<pre>		<pre>
	package() {		package() {
	mkdir -p "$pkgdir"		mkdir -p "$pkgdir/usr/lib"
	mv "$builddir"/.cabal "$builddir"/$pkgname		mv "$builddir"/.cabal "$builddir"/$pkgname
	mv "$builddir"/$pkgname "$pkgdir"/usr/lib/		mv "$builddir"/$pkgname "$pkgdir"/usr/lib/

Orson Teodoro: Add rough draft

2018-02-06T23:04:39Z

Add rough draft

New page

'''Packaging Haskell software''' may require specific versions of dependencies which the Alpine package system is not suited for. Alpine does not have an elaborate slot system, allowing for multiple minor and major versions to be installed, like Gentoo does but assumed that packages are are latest version for that release of Alpine or Edge. Alpine can achieve a slot system but requires separate package like how llvm (llvm5- llvm4-) and python (python3- and python4-) are handled. Each package dependencies along with the main program will be placed in a sandbox. We will describe boilerplate template you can use to create a package that depends on Haskell. Haskell uses a package manager called cabal which dumps the contents into a .cabal folder in the current directory. Alpine uses ghc (Glasgow Haskell Compiler) for Haskell support.

At this time, there is no site directory where all Haskell programs should go.

You need to have this make depends:

makedepends="ghc cabal"

Your prepare() statement should look like:

prepare() {
cd "$builddir"
cabal sandbox init
cabal configure --prefix=/usr
}

Your build() statement should look like:

build() {
# the cabal install will automatically fetch all dependencies and compile all dependencies and the main program
cabal install $pkgname-$pkgver
}

After <code>cabal install</code> is done, it will place all the files in a hidden folder at <code>$builddir/.cabal</code>. Dump the contents of that folder into <code>"$pkgdir"/usr/lib/$pkgname</code>. Then, then make a symlink from $pkgname/usr/lib/$pkgname/bin/$pkgname to /usr/bin/$pkgname

Your package() statement should look like:

<pre>
package() {
mkdir -p "$pkgdir"
mv "$builddir"/.cabal "$builddir"/$pkgname
mv "$builddir"/$pkgname "$pkgdir"/usr/lib/

mkdir -p "$pkgdir/usr/bin"
cd "$pkgdir/usr/bin"
ln -s /usr/lib/$pkgname/$bin/$pkgname $pkgname
}
</pre>