You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
85 lines
3.0 KiB
85 lines
3.0 KiB
## |
|
## vstr.spec -- OpenPKG RPM Package Specification |
|
## Copyright (c) 2000-2022 OpenPKG Project <http://openpkg.org/> |
|
## |
|
## Permission to use, copy, modify, and distribute this software for |
|
## any purpose with or without fee is hereby granted, provided that |
|
## the above copyright notice and this permission notice appear in all |
|
## copies. |
|
## |
|
## THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED |
|
## WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF |
|
## MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. |
|
## IN NO EVENT SHALL THE AUTHORS AND COPYRIGHT HOLDERS AND THEIR |
|
## CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, |
|
## SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT |
|
## LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF |
|
## USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND |
|
## ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, |
|
## OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT |
|
## OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF |
|
## SUCH DAMAGE. |
|
## |
|
|
|
# package information |
|
Name: vstr |
|
Summary: Virtual String Library |
|
URL: http://www.and.org/vstr/ |
|
Vendor: James Antill |
|
Packager: OpenPKG Project |
|
Distribution: OpenPKG Community |
|
Class: EVAL |
|
Group: Libraries |
|
License: LGPL |
|
Version: 1.0.15 |
|
Release: 20080101 |
|
|
|
# list of sources |
|
Source0: http://www.and.org/vstr/latest/vstr-%{version}.tar.bz2 |
|
|
|
# build information |
|
BuildPreReq: OpenPKG, openpkg >= 20160101, make |
|
PreReq: OpenPKG, openpkg >= 20160101 |
|
|
|
%description |
|
Vstr is a string library, designed so you can work optimally with |
|
readv(2)/writev(2) for input/output. This means that, for instance, |
|
you can readv(2) data to the end of the string and writev(3) data |
|
from the beginning of the string without having to allocate or move |
|
memory. It also means that the library is completely happy with data |
|
that has multiple zero bytes in it. This design constraint means |
|
that unlike most string libraries Vstr doesn't have an internal |
|
representation of the string where everything can be accessed from |
|
a single "char *" pointer in C, the internal representation is of |
|
multiple "blocks" or nodes each carrying some of the data for the |
|
string. This model of representing the data also means that as a |
|
string gets bigger the Vstr memory usage only goes up linearly and |
|
has no inherent copying. |
|
|
|
%track |
|
prog vstr = { |
|
version = %{version} |
|
url = http://www.and.org/vstr/latest/ |
|
regex = vstr-(__VER__)\.tar\.bz2 |
|
} |
|
|
|
%prep |
|
%setup -q |
|
|
|
%build |
|
CC="%{l_cc}" \ |
|
CFLAGS="%{l_cflags -O}" \ |
|
./configure \ |
|
--prefix=%{l_prefix} \ |
|
--disable-shared |
|
%{l_make} %{l_mflags -O} |
|
|
|
%install |
|
%{l_make} %{l_mflags} install AM_MAKEFLAGS="DESTDIR=$RPM_BUILD_ROOT" |
|
rm -rf $RPM_BUILD_ROOT%{l_prefix}/share/doc |
|
%{l_rpmtool} files -v -ofiles -r$RPM_BUILD_ROOT %{l_files_std} |
|
|
|
%files -f files |
|
|
|
%clean |
|
|
|
|