LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-19-2019, 06:19 AM   #2911
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 932

Rep: Reputation: 357Reputation: 357Reputation: 357Reputation: 357

Quote:
Originally Posted by Didier Spaier View Post
I don't think that /opt or /usr/local should be used by any package included in the distribution itself. It can be handy is some cases however for big third-party packages.
I agree with Didier, in particular the above statement. When I build packages, nothing gets put in /usr/local or /opt. In fact only program I use that gets to use /opt is the VirtualBox blob. I always had the impression this was the Slackware way when building packages. If I installed manually without building a package perhaps I would use /usr/local, since I don't seem logical to build packages to not use /usr/local or /opt.

As for ffmpeg, I use Alien Bob's version.

Last edited by chrisretusn; 02-19-2019 at 06:20 AM.
 
Old 02-19-2019, 09:00 AM   #2912
Okie
Senior Member
 
Registered: Mar 2002
Location: Oklahoma
Posts: 1,058

Rep: Reputation: 102Reputation: 102
i like /usr/local/ being empty on a stock slackware install, that way when i want to build some code that is not part of SBo i can let it go to /usr/local and it has its own world to reside in separate from / & /usr

not sure how /usr/local is classified, a sub-tree of its own? but i hope it stays as a separate usable system path for experimenting and testing
 
Old 02-19-2019, 03:12 PM   #2913
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,493
Blog Entries: 2

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
So, we keep /usr/local for non SBo'd software and $HOME for things that might change from user to user?

I think i can live with that - albeit the "local" isn't as worlds most intuitive a name we could coin to it, is it?

But why not have the SBo scripts be aware we want a $HOME local build with them? Like to be able to be supplied a $BUILDROOT as many sources are already? too odd?

(i do happen like Slackware as it stands right now).
 
Old 02-19-2019, 07:12 PM   #2914
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,807

Rep: Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534Reputation: 3534
Quote:
Originally Posted by SCerovec View Post
So, we keep /usr/local for non SBo'd software and $HOME for things that might change from user to user?
/usr/local/ is from the Filesystem Hierarchy Standard or FHS. While it isn't specifically stated in there, most take that /usr/ is for packaged software and /usr/local/ is for locally compiled software. Since SBo packages aren't required to be built on the machine they're installed on, that's why they don't use /usr/local/. If you run ./configure without any options, it defaults to /usr/local/ and has to be overridden to install elsewhere.

Quote:
Originally Posted by SCerovec View Post
But why not have the SBo scripts be aware we want a $HOME local build with them? Like to be able to be supplied a $BUILDROOT as many sources are already? too odd?
I imagine the simple answer is because packages should be expected to be available system-wide. Otherwise how would pkgtools know to handle packageA for userA and packageA for userB separately?

SBo's purpose is to provide a reproducible way to generate packages. Linux packages are expected to be installed system-wide, not per user.
 
Old 02-20-2019, 02:52 AM   #2915
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,493
Blog Entries: 2

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
But, must a user, intent to have a $HOME rooted package, inevitably be knowledgeable of "forcing the hand" for some of the many tools?

Maybe have the tool detect if it's run in non privileged mode and default to make the (odd ...) package rooted in the user's "~/" ?

I mean, i know my way around, but imagine your mother, or granmah desired to have some software on the shared home PC (advanced knitting simulator, for instance ) no other user is interested in?

Code:
$ sboinstall aks-v1.3_hotfix
Too marginal of an actual case?
 
Old 02-20-2019, 07:34 AM   #2916
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,440

Rep: Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069Reputation: 1069
What does this have to do with requests for -current?
 
1 members found this post helpful.
Old 02-20-2019, 09:02 AM   #2917
rjj
LQ Newbie
 
Registered: Mar 2016
Location: Portugal
Distribution: Slackware64
Posts: 16

Rep: Reputation: Disabled
Maybe I'm getting this wrong, but what's the problem with specifying --root to installpkg and have the package, be it from SBo or elsewhere, installed to /usr/local, $HOME, or whatever suits the user?
 
1 members found this post helpful.
Old 02-20-2019, 09:26 AM   #2918
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,751

Rep: Reputation: Disabled
Quote:
Originally Posted by rjj View Post
Maybe I'm getting this wrong, but what's the problem with specifying --root to installpkg and have the package, be it from SBo or elsewhere, installed to /usr/local, $HOME, or whatever suits the user?
Please do not add confusion to the off-topic. The argument of the --root option should be the root (/) of another system, for instance mounted as /mnt (then you'd write installpkg --root /mnt), never a sub-directory of the system from which you run installpkg.

Last edited by Didier Spaier; 02-20-2019 at 10:03 AM.
 
1 members found this post helpful.
Old 02-20-2019, 09:54 AM   #2919
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 1,493
Blog Entries: 2

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
Thanks Didier, I've got what i was looking for in this regard.

Sorry for OT
 
Old 02-20-2019, 07:25 PM   #2920
saxa
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 455

Rep: Reputation: 49
I wanted just to say thanks for recompiling lots of stuff against python3 ! Step by step would be good to move more and more
in py3 direction. Thanks Patric.
 
4 members found this post helpful.
Old 02-21-2019, 12:11 AM   #2921
drgibbon
Member
 
Registered: Nov 2014
Distribution: Slackware64 14.2
Posts: 445

Rep: Reputation: 267Reputation: 267Reputation: 267
KDE 5

*ducks*
 
1 members found this post helpful.
Old 02-21-2019, 01:46 AM   #2922
saahriktu
LQ Newbie
 
Registered: Nov 2017
Location: Stary Oskol, Russia
Distribution: Slackware
Posts: 20

Rep: Reputation: 7
xpdf-4.01
https://xpdfreader-dl.s3.amazonaws.com/xpdf-4.01.tar.gz
 
1 members found this post helpful.
Old 02-21-2019, 03:18 AM   #2923
Lockywolf
Member
 
Registered: Jul 2007
Posts: 147

Rep: Reputation: 32
Code:
/var/log/packages/PyQt-4.12.1-x86_64-3:8:PyQt: PyQt is a set of Python bindings for Trolltech's Qt application
Qt hasn't been Trolltech's for quite a while, but the slack-desk still mentions the old name.

Maybe it's time to update it?
 
1 members found this post helpful.
Old 02-21-2019, 05:31 AM   #2924
franzen
Member
 
Registered: Nov 2012
Distribution: slackware
Posts: 257

Rep: Reputation: 143Reputation: 143
Quote:
Originally Posted by Lockywolf View Post
Qt hasn't been Trolltech's for quite a while, but the slack-desk still mentions the old name.
The glibc slack-desk might also get updated.

Quote:
glibc: This package contains the GNU C libraries and header files. The GNU
glibc: C library was written originally by Roland McGrath, and is currently
glibc: maintained by Ulrich Drepper. Some parts of the library were
glibc: contributed or worked on by other people.
from https://en.wikipedia.org/wiki/GNU_C_Library :
Quote:
Steering committee disbands
In March 2012, the steering committee voted to disband itself and remove Drepper in favor of a community-driven development process, with Ryan Arnold, Maxim Kuvyrkov, Joseph Myers, Carlos O'Donell, and Alexandre Oliva holding the responsibility of GNU maintainership (but no extra decision-making power).
 
1 members found this post helpful.
Old 02-21-2019, 08:12 AM   #2925
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 954

Rep: Reputation: 442Reputation: 442Reputation: 442Reputation: 442Reputation: 442
After kernel upgrade today:
eliloconfig says
Code:
Could not prepare Boot variable: No such file or directory
And efibootmgr -o 0003 says
Code:
Could not set BootOrder: No such file or directory
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:33 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration