How to repackage package to Slackware format?

dugan · 11-09-2018, 04:18 PM

Quote:

Originally Posted by jakedp

Also, a good idea to follow this standard for where files go: https://refspecs.linuxfoundation.org...fhs/index.html

Typically, the only changes you need to make to the default folder structure are moving /usr/share/doc to /usr/doc and /usr/share/man to /usr/man.

bassmadrigal · 11-09-2018, 05:02 PM

Quote:

Originally Posted by igadoter

I need go because it is dependency for docker - and in fact I am interested in running docker.

Are you aware that docker and all of its dependencies are available on SBo? This way you won't need to duplicate the effort (although, if you want it as a learning experience, you certainly still could do it on your own).

Quote:

Originally Posted by igadoter

As I posted tarball essentially contains all needed directory structure. By default installation is under /usr/locale/. I think that tarball is just shot of generic installation. Essentially SlackBuild script should extract archive but with different leading directory path usr/ instead of usr/local. And probably /go sub directory is not needed - it is just for encapsulation. I want to see on my own eyes capabilities of docker.

It is not always as easy as just moving files from /usr/local/ to /usr/. Many times the programs are compiled with those locations hardcoded (based on the options when ./configure or equivalent is run). If you move things around, it may expect to find certain libraries in /usr/local/lib/, but they've been moved to /usr/lib/ and now the program can't find them.

dugan · 11-09-2018, 05:05 PM

Quote:

Originally Posted by bassmadrigal

Many times the programs are compiled with those locations hardcoded (based on the options when ./configure or equivalent is run). If you move things around, it may expect to find certain libraries in /usr/local/lib/, but they've been moved to /usr/lib/ and now the program can't find them.

That is true. Moving files around works best if the executable looks for its resources relative to where the executable is., e.g. ../lib and ../share.

igadoter · 11-10-2018, 05:26 AM

No matters whether go is installed under /opt or /usr/local I can build but I got the same errors. It seems that go installation is more convenient per user than system wide. Some commands can't be executed by common user due to lack of permission, say https://golang.org/doc/

Code:

$ go get golang.org/x/tour

at the end of the execution it requires writing permission in $GOROOT, whether /opt/go or /usr/local/go. So maybe just better put all this under $HOME/, till I figure out how to configure go system wide. SlackBuild script installs under /usr/lib(64)/go$VERSION/go. I can't see why it is better place to install.