Package Details: python2-keras-git 1.2.0.r106.ge54d7951-1

Git Clone URL: https://aur.archlinux.org/python-keras-git.git (read-only)
Package Base: python-keras-git
Description: Theano-based Deep Learning library (convnets, recurrent neural networks, and more)
Upstream URL: https://github.com/fchollet/keras
Licenses: MIT
Conflicts: python2-keras
Provides: python2-keras
Submitter: StreakyCobra
Maintainer: StreakyCobra
Last Packager: StreakyCobra
Votes: 1
Popularity: 0.660845
First Submitted: 2015-06-30 07:09
Last Updated: 2017-01-16 21:30

Latest Comments

gcarq commented on 2017-01-16 17:10

Please mark python-keras as conflict, i.e.:

provides=('python-keras')
conflicts=('python-keras')

StreakyCobra commented on 2016-02-22 14:39

@soupault AFAIK git packages are not updated on new release, they are updated when there are upstream changes impacting the build process. They are meant to be built on regular schedule. People who want to have packages based on upstream release should use the non-git one.

soupault commented on 2016-02-22 13:35

@streakycobra ok, thanks for the info!
Could you force the version update? 0.3.2 is already available.

StreakyCobra commented on 2015-11-21 17:16

I discussed it on this thread: https://lists.archlinux.org/pipermail/aur-general/2015-November/031786.html

This way to do it is perfectly fine, so I'll stay with it. Anyway I removed some of the makedepends that weren't necessary. (I just noticed you edited your comment compared to the mail I received, maybe you were speaking about this finally :-) )

StreakyCobra commented on 2015-11-21 15:20

I have them in make-depends because it's needed to build the packages with `extra-x86_64-build` from `devtools`. I like to build AUR packages in a chroot environment for different reasons, but indeed it forces to have all of them installed even for building only the python3 version. I'll ask on the mailing list if there is any solution, if not I'll change this.

soupault commented on 2015-11-21 08:32

why does your PKGBUILD have both Py2 and Py3 make-dependencies, which aren't really make-depends?