Found solution, it was rather easy - just put a .pth in the "official"
site-packages containing the full path to the directory being added.
On 03/04/2017 09:55 AM, Alice Wonder wrote:
I want to create RPM spec file that lets the user build the RPM with an
alternate prefix - e.g.
rpmbuild -D
I want to create RPM spec file that lets the user build the RPM with an
alternate prefix - e.g.
rpmbuild -D '_prefix /opt/whatever' -bb package.spec
That results in in the python files being placed in
/opt/whatever/lib/pythonN/site-packages and
/opt/whatever/%{_lib}/pythonN/site-packages
So you want to build something independent of the system python? Is
virtualenv and / or anaconda interesting here?
On 4 March 2017 at 17:36, Alice Wonder wrote:
> Hello,
>
> Working on a project to create clean spec files for libbitcoin for CentOS
> 7 (and eventually I
Hello,
Working on a project to create clean spec files for libbitcoin for
CentOS 7 (and eventually I want them to work in Fedora 25+ too)
These spec files must work with the user defines an alternate %{_prefix}
before building them.
This means that python components would be installed in
CentOS [centos-boun...@centos.org], On Behalf Of Johnny Hughes, spake
thusly:
> The CentOS-7-x86_64-Everything.iso (without a version) is a symlink to the
> 'lastest' Everything iso. If you look at the sha256sum file, the last
> Everything file listed will be the version you use.
>
> Currently
On 03/03/2017 09:17 PM, Darr247 wrote:
> I downloaded CentOS-7-x86_64-Everything.iso (8,233,418,752 bytes) by
> clicking on the 'Everything' link in the 'Rolling' line on
> https://wiki.centos.org/Download (supposedly the 1611 build).
>
> But when I look in the sha256sum.txt file from
>
On 03/03/17 22:56, Fred Smith wrote:
On Fri, Mar 03, 2017 at 12:03:52PM -0800, Akemi Yagi wrote:
On Fri, Mar 3, 2017 at 9:16 AM, Lamar Owen wrote:
All,
This is just a heads-up that the new C7 update kernel breaks ABI
compatibility, at least as far as using the ELrepo nVidia
I had a similar issue. On one of my vms. My host rebooted while the vm was
running its update. I had to remove the kernel then reinstall and it
corrected the issue.
On Sat, Mar 4, 2017, 7:37 AM Günther J. Niederwimmer
wrote:
> Hello,
>
> the last update brings much Problems ?
Hello,
the last update brings much Problems ?
On my System the most KVM client have a crashed yum
after reboot the new kernel is broken and have a panic screen
I have to reboot to a older kernel ?
The first I have to run
yum-complete-transaction
afterward i have to reinstall the kernel ??
9 matches
Mail list logo