LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices

Reply
 
Search this Thread
Old 03-22-2013, 10:42 AM   #16
mreff555
Member
 
Registered: Sep 2011
Location: Philly
Distribution: Gentoo
Posts: 443

Original Poster
Rep: Reputation: Disabled

Me too. I haven't completely figured out how they work yet but they are much simpler than e-builds making them easier to tweak.

Oh btw, is there a standardized place I should be keeping my builds? Right now I just have them in a directory I set up called "/root/packages".
 
Old 03-22-2013, 11:07 AM   #17
JWJones
Member
 
Registered: Jun 2009
Location: Cascadia
Distribution: Slackware, LinuxBBQ, OpenBSD, Mac OSX
Posts: 723

Rep: Reputation: 186Reputation: 186
Quote:
Originally Posted by mreff555 View Post
Oh btw, is there a standardized place I should be keeping my builds? Right now I just have them in a directory I set up called "/root/packages".
Good question. I'll wait for more experienced slackers to answer that. I have mine in a folder in user/home at the moment.
 
Old 03-23-2013, 09:09 AM   #18
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,064
Blog Entries: 1

Rep: Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374Reputation: 1374
Member Response

Hi,

Welcome to Slackware!
Quote:
Originally Posted by mreff555 View Post
Me too. I haven't completely figured out how they work yet but they are much simpler than e-builds making them easier to tweak.

Oh btw, is there a standardized place I should be keeping my builds? Right now I just have them in a directory I set up called "/root/packages".
Personal choice, maybe on a secondary storage for future use elsewhere so you can build on other installs.
From http://docs.slackware.com/
Quote:
The Slackware Way Slackware maintains a KISS philosophy. It uses text files for configuration instead of GUI configuration programs like many other distributions.
The main highlights and features of Slackware and the philosophy behind the distribution can be summarized as below.

Distribution Philosophy

Slackware is:
  • A distribution that can be installed entirely offline with the CD/DVD set.
  • A distribution which is released when stable and not according to a fixed schedule. Every release of Slackware Linux is thoroughly tested by the Slackware team and the community. Slackware places high value on stability rather than the “newness” or “freshness” of software.
  • A distribution where “simplicity” is preferred over “convenience.” The lack of GUI helpers (common in many other commercial distributions) for system administration tasks is a case in point.
  • A distribution where system configuration and administration is done through simple ncurses helper scripts or by directly editing well-commented configuration files through a text editor.
  • A distribution that prefers to package “vanilla” software or software that hasn't been modified from upstream development. Little or no patching is done to upstream software and as a result, the software found in Slackware works as closely to what was intended by the original creators as practically possible.
  • A distribution that does not add layers of abstraction or complexity on top of existing solutions. For instance, Slackware package management is handled by simple scripts acting on compressed tarball package files (*.tgz, *.txz, *.tbz) and there is no dependency handling for package management.
  • A distribution which abides by the common-sense dictum “if it's not broken, don't fix it.”
  • A distribution where the major decisions are taken by the BDFL (Benevolent Dictator for Life, the current chief maintainer Patrick Volkerding) and where the development process is more closed than purely community based distributions. As a result, Slackware is highly focused on its core strengths and values and does not cater to every preference of its community or others. For this reason, there is less pressure on the Slackware development team to be popular and cater to the larger mass market.

Slackware Doc Project is a very useful tool for everyone.
 
  


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
LXer: Android Shmandroid. Give me Apple support or give me nothing. LXer Syndicated Linux News 0 02-16-2012 03:50 PM
LXer: Give Me Liberty or Give Me Eth LXer Syndicated Linux News 0 05-18-2010 02:41 PM
Please give me 5 reason why to use Slack? banana2 Slackware 21 05-31-2005 12:27 PM
I give up on slack lmanwarren Slackware 2 05-02-2005 11:22 AM


All times are GMT -5. The time now is 12:11 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration