VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Author Topic: documentation project  (Read 6526 times)

wigums

  • Guest
documentation project
« on: September 21, 2015, 01:06:59 pm »
we are working on a documentation project. a "how-to" of sorts to provide easy to follow instructions on things like
upgrading a kernel or how to make a bootable usb stick. does anyone have any suggestions of documentation they
would like on a specific subject?

theres no way we could ever compare to a project like arch wiki but we'll add documentation on various topics as we go
and it will grow and be a nice resource for our users
Logged

sledgehammer

  • Vectorian
  • ****
  • Posts: 1527
Re: documentation project
« Reply #1 on: September 21, 2015, 08:36:07 pm »
I would like some documentation on how to build a slackware package that will run on VL 7.1-64 from source.   How to find the dependencies it needs.  And how to use the existing VL install from source program. 


Logged
VL7.0 xfce4 Samsung RF511

askfor

  • Member
  • *
  • Posts: 33
  • user
Re: documentation project
« Reply #2 on: October 29, 2015, 07:11:18 pm »
Sledgehammer, you might want to check available slapt-get documentation.
 
Logged

M0E-lnx

  • Administrator
  • Vectorian
  • *****
  • Posts: 3497
Re: documentation project
« Reply #3 on: October 30, 2015, 07:25:03 am »
Quote from: sledgehammer on September 21, 2015, 08:36:07 pm
I would like some documentation on how to build a slackware package that will run on VL 7.1-64 from source.   How to find the dependencies it needs.  And how to use the existing VL install from source program.
I can suggest getting familiar with the sbbuilder documentation.  You usually only need to pass a couple of arguments to it, and it will generate a working slackbuild for you.  See 'sbbuilder --manual' for help.

Unfortunately, there is no easy way to determine what a package may or may not need.  That depends on what you currently have installed.  That portion of the process is determinted by trial and error, until it passes.
Logged

wigums

  • Guest
Re: documentation project
« Reply #4 on: October 30, 2015, 11:22:42 am »
and by some crafty interpretation of the build logs via your secret yoda decrypter ring
Logged

askfor

  • Member
  • *
  • Posts: 33
  • user
Re: documentation project
« Reply #5 on: October 30, 2015, 12:53:21 pm »
I suppose adapting existing Slackware packages might be a good start. I have not tried yet. However I installed couple of Slackware packages which I needed, and wasn't able to find in VL repositories. I have noticed that, at least, some of them, contain information what else is needed in human readable form. The information is displayed when one installs them with installpkg. I suppose there are other ways to read that information.
Logged

sledgehammer

  • Vectorian
  • ****
  • Posts: 1527
Re: documentation project
« Reply #6 on: November 02, 2015, 09:49:45 pm »
My point is that as linux ages and gets more popular, many of the flavors have become rather boring.  Debian is an example.  Going outside the Debian repositories is a no-no.  But Vector is fun, in my case, because I am less fearful of breaking it. I find that when I want to try something new, I do it on 'vector.  Problem is that the new program generally comes in some other format....usually it seems ubuntu or red hat.  The trouble with make, make install etc is that if the program doesn't work, its difficult to uninstall it. 

I see Vector's notch as being a place where source programs can be installed.  Most vendors provide a source version.  Dependencies will always be a problem, and changing this may break that.  But if we vectorites could fearlessly opt for the source as the default and install from source, perhaps we could recapture some of the fun in computing.

I know I used to install from source and slackbuilds a lot.

Just my two bits worth.

You guys are doing a great job.  I regret having too little time to be of much help.
Logged
VL7.0 xfce4 Samsung RF511

wigums

  • Guest
Re: documentation project
« Reply #7 on: November 03, 2015, 11:58:07 am »
i admin my vector boxen the exact same as i do my slackware,
manually. i use existing slackbuilds and when something isnt available
i use makepkg or use a slackbuild template and edit it.

as far as building packages for vector linux we have a slackbuild
creater named sbbuilder and its in the repos, anyone can dl it.

ideally you would have a clean build enviroment for which we use docker,
which is also available and pretty easy to set up. you dont HAVE
to to use docker. you can run sbbuilder on your box and submit the slackbuild.

we use bitbucket for version control and thats how you would submit
said slackbuild.

we do have alot of documentation already written and available
but still needs some work. 7.2 is coming fast and the crew is working
just as fast to get the next release ready.

i personally hope to get enough time during 7.2s life to have the entire
project well on its way to completion (it will never really be "completed,
new stuff pops up all the time") the first set of docs im going to work on is packaging from start to finish. it really is rather easy once once ya get the hang of it um but the
point is its on the back burner now. its coming but we have some other things
to do first. so this is the long and short of packaging
Logged