It looks like you're new here. If you want to get involved, click one of these buttons!
Hi Matthias-
I'm trying to install x-sec package on a virtual windows server.
I'm getting the error message above, not sure why. Does not seem like access issue since I am able to get to the Github web page on my browser.
Is there a way to download package to c: drive then install it from there?
Thanks,
Comments
You can basically try later - maybe there is an issue with the server. Right now, everything is working fine.
If you have trouble downloading, that is often a Firewall issue. Maybe you organization is blocking GitHub?
In that case you should talk to your IT guys. Downloading is possible - eventually all packages end in "c:\users\\KLayout\salt\". But the specific details are depending on the package.
Matthias
I always have trouble navigating git and finding the right
thing to download, unless I have clear simple instructions
about setting up the git image (?) and pulling. I can't find
that, specifically, in the doc-chain. It would be a good
addition to build.html for first time git source users.
While I'm wishing for installation ease, how about a script or
even a simple list of all dependencies? I've installed klayout
to fresh Linux installs a dozen or more times and always
end up chasing packages, fail-message after fail-message
until done with ./configure (or is it ./build now?) working clean.
For my purposes I would like to grab and hold the entire
source tree including dependency sources. And what about
the dependencies of the dependencies? Could I even dream
of dreaming about an auto-compile-all-from-source rack?
Not just klayout but any / all dependencies that are discovered
missing or stale at install time?
Anyway seems like maybe the kind of thing that would just
fall out the bottom of development work, but anyone who
knows what they're doing wouldn't need help with, and that
doesn't describe some of us.
Hi @dick_freebird,
You mean, when building KLayout from sources?
I am afraid there is no common recipe and KLayout already has as few dependencies as possible.
I am trying to document the required Linux packages here: https://www.klayout.de/build.html (scroll down to "Building KLayout on Linux").
Matthias
My organization is really harsh about apps accessing external links on the network.
However when browsing through a std browser, it let's you access and copy files.
It would be nice if i could just copy latest packages from repository, save it locally, then direct Klayout to take it from there instead of external repository.
Regards,
Hello @mikamar,
Please attempt the steps shown in the images below.
If Windows, %USERPROFILE%\KLayout\salt\
Many thanks @sekigawa for this tutorial!
The easiest way to do that in my experience is to download all needed packages on a device outside the restricted zone and transfer the whole "salt" folder to your device inside the restricted zone.
However, this requires you to repeat the step when you have an update.
It is also possible to use a local Subversion server to host packages inside your organization. You can use the "KLAYOUT_SALT_MINE" environment variable to redirect KLayout to a different repository URL. KLayout will read a file called "repository.xml" from there which is the package index. You can set up your own package server, serving your own package index. This is a way to provide non-public packages to your internal community.
Matthias
Tutorial is a big help for git-clueless like me.
A semi-smart script which would determine the
target-host "all needed packages" and maybe also
inquire about the build desired particulars (like all
the associated options, are they desired or required)
and pick the right source-pile and pull it all, would
be ideal (as there's options and dependencies that
Dumb Users struggle to figure out, IME).
Maybe some config-specific Makefiles for the most
commonly desired configs from Dumb Users (the
ones needing help to navigate) and a cheat sheet,
while we're at it?
Hi @dick_freebird,
By though of using KLayout outside the restricted zone to install the packages there. This can be a different machine not inside the restricted network.
Basically, KLayout keeps packages in a folder called "salt" inside the home area. This is "/home//.klayout/salt" on Linux and "C:\users\\KLayout\salt" on Windows. To transfer the installed packages, simply zip this folder, transfer it into the restricted area and unzip it there in the same place. This will make the packages available, but you can't upgrade them there directly or install new packages.
Manually pulling packages yourself (without KLayout) can be done as well, but there are two protocols (git and svn) and one additional complication as package files can sit somewhere deeper inside the hierarchy of a git project. I think the other-klayout-as-a-client approach is way easier.
Matthias