Add expected package
This commit is contained in:
@@ -108920,6 +108920,47 @@ cleaner, which will allow to add new features in the future.</Description>
|
||||
</Update>
|
||||
</History>
|
||||
</SpecFile>
|
||||
<SpecFile>
|
||||
<Source>
|
||||
<Name>expected</Name>
|
||||
<Homepage>https://github.com/TartanLlama/expected</Homepage>
|
||||
<Packager>
|
||||
<Name>Safa Arıman</Name>
|
||||
<Email>safa@ariman.gen.tr</Email>
|
||||
</Packager>
|
||||
<License>CC0</License>
|
||||
<IsA>library</IsA>
|
||||
<PartOf>programming.library</PartOf>
|
||||
<Summary xml:lang="en">Single header implementation of std::expected with functional-style extensions.</Summary>
|
||||
<Summary xml:lang="tr">Single header implementation of std::expected with functional-style extensions.</Summary>
|
||||
<Description xml:lang="en">std::expected is proposed as the preferred way to represent object which will either have an expected value, or an unexpected value giving information about why something failed. Unfortunately, chaining together many computations which may fail can be verbose, as error-checking code will be mixed in with the actual programming logic. This implementation provides a number of utilities to make coding with expected cleaner.</Description>
|
||||
<Description xml:lang="tr">std::expected is proposed as the preferred way to represent object which will either have an expected value, or an unexpected value giving information about why something failed. Unfortunately, chaining together many computations which may fail can be verbose, as error-checking code will be mixed in with the actual programming logic. This implementation provides a number of utilities to make coding with expected cleaner.</Description>
|
||||
<Archive type="targz" sha1sum="2ce5120ef6b4238b092a73214a48516462f809ce" name="v1.0.0.tar.gz">https://github.com/TartanLlama/expected/archive/v1.0.0.tar.gz</Archive>
|
||||
<BuildDependencies>
|
||||
<Dependency>cmake</Dependency>
|
||||
<Dependency>git</Dependency>
|
||||
<Dependency>catch2</Dependency>
|
||||
</BuildDependencies>
|
||||
<SourceURI>programming/library/expected/pspec.xml</SourceURI>
|
||||
</Source>
|
||||
<Package>
|
||||
<Name>expected-devel</Name>
|
||||
<Files>
|
||||
<Path fileType="header">/usr/include</Path>
|
||||
<Path fileType="doc">/usr/share/doc</Path>
|
||||
<Path fileType="data">/usr/share/cmake</Path>
|
||||
</Files>
|
||||
</Package>
|
||||
<History>
|
||||
<Update release="1">
|
||||
<Date>2020-03-17</Date>
|
||||
<Version>1.0.0</Version>
|
||||
<Comment>First release</Comment>
|
||||
<Name>Safa Arıman</Name>
|
||||
<Email>safa@ariman.gen.tr</Email>
|
||||
</Update>
|
||||
</History>
|
||||
</SpecFile>
|
||||
<SpecFile>
|
||||
<Source>
|
||||
<Name>libnih</Name>
|
||||
|
||||
@@ -1 +1 @@
|
||||
1cfbb57edb0b0f9c4a95446a533cad732c60ed2e
|
||||
594a689dbbe031e3dc2d7703ca426eed6b8d5d39
|
||||
Binary file not shown.
@@ -1 +1 @@
|
||||
6a3d7073f375e0310217590e5fed81f7e5f74b37
|
||||
8e3af7f8cee8c7bb0eb1a1a67891a7ca7ade83bd
|
||||
@@ -0,0 +1,30 @@
|
||||
#!/usr/bin/env python
|
||||
# -*- coding: utf-8 -*-
|
||||
#
|
||||
# Licensed under the GNU General Public License, version 3.
|
||||
# See the file http://www.gnu.org/licenses/gpl.txt
|
||||
|
||||
from pisi.actionsapi import cmaketools, shelltools
|
||||
from pisi.actionsapi import pisitools
|
||||
|
||||
|
||||
def setup():
|
||||
cmaketools.configure('-B build')
|
||||
|
||||
|
||||
def build():
|
||||
shelltools.cd('build')
|
||||
cmaketools.make()
|
||||
|
||||
|
||||
def check():
|
||||
shelltools.cd('build')
|
||||
shelltools.system('./tests')
|
||||
|
||||
|
||||
def install():
|
||||
shelltools.cd('build')
|
||||
cmaketools.install()
|
||||
|
||||
pisitools.dodoc('../COPYING')
|
||||
pisitools.insinto('/usr/bin', 'sl')
|
||||
@@ -0,0 +1,41 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE PISI SYSTEM "http://www.pisilinux.org/projeler/pisi/pisi-spec.dtd">
|
||||
<PISI>
|
||||
<Source>
|
||||
<Name>expected</Name>
|
||||
<Homepage>https://github.com/TartanLlama/expected</Homepage>
|
||||
<Packager>
|
||||
<Name>Safa Arıman</Name>
|
||||
<Email>safa@ariman.gen.tr</Email>
|
||||
</Packager>
|
||||
<License>CC0</License>
|
||||
<IsA>library</IsA>
|
||||
<Summary>Single header implementation of std::expected with functional-style extensions.</Summary>
|
||||
<Description>std::expected is proposed as the preferred way to represent object which will either have an expected value, or an unexpected value giving information about why something failed. Unfortunately, chaining together many computations which may fail can be verbose, as error-checking code will be mixed in with the actual programming logic. This implementation provides a number of utilities to make coding with expected cleaner.</Description>
|
||||
<Archive sha1sum="2ce5120ef6b4238b092a73214a48516462f809ce" type="targz">https://github.com/TartanLlama/expected/archive/v1.0.0.tar.gz</Archive>
|
||||
<BuildDependencies>
|
||||
<Dependency>cmake</Dependency>
|
||||
<Dependency>git</Dependency>
|
||||
<Dependency>catch2</Dependency>
|
||||
</BuildDependencies>
|
||||
</Source>
|
||||
|
||||
<Package>
|
||||
<Name>expected-devel</Name>
|
||||
<Files>
|
||||
<Path fileType="header">/usr/include</Path>
|
||||
<Path fileType="doc">/usr/share/doc</Path>
|
||||
<Path fileType="data">/usr/share/cmake</Path>
|
||||
</Files>
|
||||
</Package>
|
||||
|
||||
<History>
|
||||
<Update release="1">
|
||||
<Date>2020-03-17</Date>
|
||||
<Version>1.0.0</Version>
|
||||
<Comment>First release</Comment>
|
||||
<Name>Safa Arıman</Name>
|
||||
<Email>safa@ariman.gen.tr</Email>
|
||||
</Update>
|
||||
</History>
|
||||
</PISI>
|
||||
@@ -0,0 +1,8 @@
|
||||
<?xml version="1.0" ?>
|
||||
<PISI>
|
||||
<Source>
|
||||
<Name>expected</Name>
|
||||
<Summary xml:lang="tr">Single header implementation of std::expected with functional-style extensions.</Summary>
|
||||
<Description xml:lang="tr">std::expected is proposed as the preferred way to represent object which will either have an expected value, or an unexpected value giving information about why something failed. Unfortunately, chaining together many computations which may fail can be verbose, as error-checking code will be mixed in with the actual programming logic. This implementation provides a number of utilities to make coding with expected cleaner.</Description>
|
||||
</Source>
|
||||
</PISI>
|
||||
Reference in New Issue
Block a user