Skip to content
Permalink
e77f32591d
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
91 lines (90 sloc) 2.77 KB
." manpage of beesh
."
." Copyright (C) 2009-2016
." Marius Tolzmann <m@rius.berlin>
." Tobias Dreyer <dreyer@molgen.mpg.de>
." and other bee developers
."
." This file is part of bee.
."
." bee is free software; you can redistribute it and/or modify
." it under the terms of the GNU General Public License as published by
." the Free Software Foundation, either version 3 of the License, or
." (at your option) any later version.
."
." program is distributed in the hope that it will be useful,
." but WITHOUT ANY WARRANTY; without even the implied warranty of
." MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
." GNU General Public License for more details.
."
." You should have received a copy of the GNU General Public License
." along with this program. If not, see <http://www.gnu.org/licenses/>.
.TH "beesh" "1" "2012-08-31" "bee @BEE_VERSION@" "bee package management"
.SH "HOWTO WRITE A BEE-FILE"
.SS "I have an url and want to build that stuff."
The simplest way to create a bee file is to run
.BR "bee init <url-to-sources>" .
This will end up in a bee-file looking like
.P
.RS
.TQ
#!/bin/env beesh
.TQ
SRCURL[0]="http://<url-to-sources>"
.RE
.P
To make it easier to you to apply changes to your build your bee-file contains some commented stuff too.
.SS "Is there a way to customize the build process?"
.P
We provide you with a set of functions that you may adjust for your needs. These are
.BR mee_patch ", " mee_configure ", " mee_build " and " mee_install .
To each of these functions you may append
.BR _pre " or " _post .
Use these functions to adjust the build process to your needs.
.SS "Where are my .la files? or I don't want that documentation stuff!"
.B bee
supports two ways of excluding files so they won't appear in your final bee-package. On the one hand there are many files
that are automatically excluded by bee and one the other hand you can specify files that you wnat to exclude from your
bee-package.
.P
To disable the bee built-in auto exclusion add
.B disable_autoexclusion
to your bee-file.
.P
To exclude files use
.B EXCLUDE
and provide a quoted 'space' separated list of regular expressions.
.P
.RS
EXCLUDE=( ^/usr/share/gtk-doc ^/usr/share/doc )
.RE
.SS "Argh! My build takes so much time.."
You might discover that
.B bee
takes quiet a lot time after packaging your software. This is because
.B bee
creates an archive of all build process related files (sources, patches, ..). If you don't want this run your bee-file with
.P
.RS
bee-file-1.0-0.bee
.B \-\-no-archive-build
.RE
.SH "AUTHORS"
.P
.MT m@rius.berlin
Marius Tolzmann
.ME
.P
.MT dreyer@molgen.mpg.de
Tobias Dreyer
.ME
.SH "SEE ALSO"
.BR bee (1)
.BR bee\-check (1)
.BR bee\-download (1)
.BR bee\-init (1)
.BR bee\-install (1)
.BR bee\-list (1)
.BR bee\-query (1)
.BR bee\-remove (1)
.BR bee\-update (1)