| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.44, Repoman-2.3.10
|
|
|
|
|
|
| |
version replaced inplace by upstream
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Removal per https://bugs.gentoo.org/573264
Package-Manager: Portage-2.3.40, Repoman-2.3.9
RepoMan-Options: --force
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
And EAPI downgrade, since eclass does not yet support
EAPI 7.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
CXX/CXXFLAGS are still not respected for bundled samtools subdirectory.
https://github.com/gpertea/stringtie/issues/185#issuecomment-400637035
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
| |
Thanks to @kiwifb for spotting two improperly used variablenames
https://github.com/gentoo/sci/commit/a1d0487c37ba900c1f239f5d73f7d429f018359d#commitcomment-29493393
https://github.com/gentoo/sci/commit/a1d0487c37ba900c1f239f5d73f7d429f018359d#commitcomment-29493465
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
Thanks to @kiwifb
https://github.com/gentoo/sci/commit/a1d0487c37ba900c1f239f5d73f7d429f018359d#commitcomment-29493393
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/gpertea/gclib/issues/2#issuecomment-400125651
There is a bit of confusion here, this "library" is not meant to be
a typical object library (no binary static file is being built) and
certainly not meant to be built and installed globally into some
${prefix}/lib/ with corresponding headers under ${prefix}/include
or so...
It's just a loose collection of reusable source code which I directly
include/source into a few of my bioinformatics projects, at compile
time, as needed. As such there should be no reason to install it
separately, system wide! (and I would advise against it).
Moreover, the Makefile included here was simply meant for some quick
testing during development, not for distribution. I have some simple
scripts included in the actual projects themselves (e.g. gffread)
which are pulling the minimum necessary source code files from the
gclib directory in the process of creating a custom release tarball
for distribution, which can then be found on the official release web
page for each project (e.g. for gffread is
http://ccb.jhu.edu/software/stringtie/dl/gffread-0.9.12.tar.gz). That
"official" source code release tarball already includes the gclib source
files that are needed to build the project -- so I would advise various
distributions to use those releases instead as they should build properly
with the gclib code "frozen" at the time of that particular release.
Since gclib code is in continuous development/tweaking, as the various
projects using it are too, there is no guarantee that the various
automatic github releases are going to be all build compatible all the
time (though I do try to keep the "master" branches in sync and ready
to build, but beyond those "official", manually tested releases, it's
hard to keep multiple projects in sync all the time).
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/gpertea/stringtie/issues/185#issuecomment-400128090
https://github.com/gpertea/stringtie/issues/186#issuecomment-400131844
Therefore, keep local copy of gclib and samtools.
Still it does not compile for me with gcc-7.3.0
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The soucre tree is not made to use site-wide installed headers from
gclib. I am not going to figure out git commit tag of gclib automagically
bundled into some gffread binary when gffread was released (to make
a dedicated gclib-$commitnr.tar.gz file for Gentoo/Debian/etc. and to
include it into SRC_URI here so gffread could use it.
It is the task for upstream author to properly document required versions
of dependencies and release them properly.
https://github.com/gpertea/gffread/issues/26#issuecomment-400134376
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Is a mixture of gclib object and gffcompare objects, hence
the download of two tar.gz files.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
| |
Does not compile, will report upstream.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Appears bundled in sci-biology/gffread , sci-biology/stringtie and
probably in even more packages.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
Also use properly named CXX and CXXFLAGS variables, respect their initial
values.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
| |
https://github.com/COMBINE-lab/salmon/issues/181#issuecomment-367800400
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
The -9999 won't work as the SRC_URI section is not respected,
hence is commented out.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
This zaps all calls to curl downloads during compile time
except those for Google tbb. It should not get executed anyway
as the dev-cpp/tbb dependency is enforced.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Document zillions of cryptic dependencies of a lousy package
https://github.com/Kingsford-Group/libgff/issues/1
https://github.com/COMBINE-lab/salmon/issues/236
https://github.com/COMBINE-lab/salmon/issues/19
Incomplete install docs are deemed to be at:
http://salmon.readthedocs.io/en/latest/building.html#requirements-for-building-from-source
Try the command below to see yourself:
salmon-0.10.2 $ find . -type f | xargs grep curl 2>/dev/null
Thanks to @kiwifb for comments at
https://github.com/gentoo/sci/commit/a1d0487c37ba900c1f239f5d73f7d429f018359d
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
| |
cmake does not detect boost for me although the errors speak of pthread
and not boost. Older version could probably be dropped soon.
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|