https://www.slackwiki.com/api.php?action=feedcontributions&user=Sombriks&feedformat=atomSlackWiki - User contributions [en]2024-03-29T07:47:07ZUser contributionsMediaWiki 1.40.0https://www.slackwiki.com/index.php?title=SlackWiki:Community_Portal&diff=403SlackWiki:Community Portal2010-08-21T20:32:48Z<p>Sombriks: </p>
<hr />
<div>====[http://www.slackwarebrasil.org GUS-BR]====<br />
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)<BR><br />
[http://www.slackwarebrasil.org www.slackwarebrasil.org ]<br />
pt-br Wiki<br />
[http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]<br />
<BR><br />
<br />
====[http://slacky.eu/ Slacky.eu]====<br />
The Italian Slackware Community<BR><br />
[http://slacky.eu/ http://slacky.eu]<br />
<BR><br />
====[http://slackware.linux.or.id Indonesian Slackware Community]====<br />
[http://slackware.linux.or.id http://slackware.linux.or.id]</div>Sombrikshttps://www.slackwiki.com/index.php?title=SlackWiki:Community_Portal&diff=402SlackWiki:Community Portal2010-08-21T20:32:16Z<p>Sombriks: /* GUS-BR */</p>
<hr />
<div>====[http://www.slackwarebrasil.org GUS-BR]====<br />
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)<BR><br />
[http://www.slackwarebrasil.org www.slackwarebrasil.org ]<br />
pt-br Wiki<br />
[http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]<br />
<BR><br />
<br />
====[http://slacky.eu/ Slacky.eu]====<br />
The Italian Slackware Community<BR><br />
[http://slacky.eu/ http://slacky.eu]<br />
<BR><br />
====[http://slackware.linux.or.id Indonesian Slackware Community]====<br />
[http://slackware.linux.or.id http://slackware.linux.or.id]</div>Sombrikshttps://www.slackwiki.com/index.php?title=Converting_From_CRLF_To_LF&diff=373Converting From CRLF To LF2010-06-16T23:17:37Z<p>Sombriks: </p>
<hr />
<div>=Explanation=<br />
<br />
There are several ways of converting the CRLF combination to LF and vice-versa. The simplest one under Slackware is to use the tools <code>fromdos</code> and <code>todos</code>, which receive the file from the standard input and write the result to the standard output. They are part of the <code>bin</code> package.<br />
<br />
=Examples=<br />
<br />
$ fromdos <input_file >output_file # Converts CRLF to LF<br />
$ todos <input_file >output_file # Converts LF to CRLF<br />
<br />
Also you could play with tr (from CRLF to LF):<br />
<br />
$ tr -d '\r' < input_file > output_file<br />
<br />
[[Category:Tips]]</div>Sombrikshttps://www.slackwiki.com/index.php?title=User:Sombriks&diff=359User:Sombriks2010-05-18T21:43:45Z<p>Sombriks: Created page with '= $ whoami = I'm a slack-user since 10.1 version. Oh i remember, i've started with serious linux with the last Slackware version shipping GNOME by the hands of Pat. = vmstat = …'</p>
<hr />
<div>= $ whoami =<br />
<br />
I'm a slack-user since 10.1 version. Oh i remember, i've started with serious linux with the last Slackware version shipping GNOME by the hands of Pat.<br />
<br />
= vmstat =<br />
<br />
Actually i'm mostly a java developer, with some javascript and C over the week. I never tried other distros since then, since slackware have sun jdk/jre, firefox and gcc i'm well served.</div>Sombrikshttps://www.slackwiki.com/index.php?title=Building_A_Package&diff=358Building A Package2010-05-18T19:38:37Z<p>Sombriks: </p>
<hr />
<div>[[Category:Tutorials]]<br />
<br />
= Intro =<br />
<br />
This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.<br />
<br />
== The good and decent way ==<br />
<br />
Configure and compile the source as you usually do:<br />
./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc<br />
make<br />
<br />
Make a temporary destination directory available:<br />
mkdir /tmp/build<br />
<br />
Install into the temporary directory:<br />
make install DESTDIR=/tmp/build<br />
<br />
Now strip libs/bins within the temporary directory:<br />
strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*<br />
<br />
You also want to make sure that anything in <tt>/usr/man</tt> is gzipped before you make the package:<br />
gzip -9 /tmp/build/usr/man/man?/*.?<br />
<br />
Create the <tt>install</tt> directory, this is where the description and install script will be stored:<br />
cd /tmp/build<br />
mkdir install<br />
cd install<br />
<br />
Using a text editor, create a file called <tt>slack-desc</tt> and fill it with the following contents:<br />
<br />
|-----handy-ruler------------------------------------------------------|<br />
app: Application Name (Short/Brief description)<br />
app:<br />
app: Enter a description of the package you are building.<br />
app: All 11 "app:" lines must be present<br />
app: "app" needs to be your application name.<br />
app: The handy-ruler is there to help you, these lines should not exceed<br />
app: 79 characters.<br />
app:<br />
app:<br />
app:<br />
app:<br />
<br />
Create the actual package:<br />
cd /tmp/build<br />
makepkg ../app-version-arch-tag.tgz<br />
<br />
''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc. Official slackware packages have only numbers as tags.)''<br />
<br />
When prompted to recreate symbolic links, say <tt>yes</tt><br><br />
When prompted to reset permissions, say <tt>no</tt><br />
<br />
''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''<br />
<br />
If all went well, you can now install the package.<br />
cd ..<br />
installpkg app-version-arch-tag.tgz<br />
<br />
<br />
== The "i don't have time" way ==<br />
<br />
Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this: <br />
./configure --prefix=/usr<br />
make install DESTDIR=$(pwd)/PACKAGE<br />
cd $(pwd)/PACKAGE<br />
makepkg -l y -c n ../app-version-arch-tag.tgz<br />
installpkg ../app-version-arch-tag.tgz<br />
<br />
Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.<br />
<br />
----<br />
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].<br />
----</div>Sombriks