Makeworld

I am thinking of rebuilding a series of packages to include all the docs. Right now makepkg strips out a lot of the docs from the packages.
My plan is as follows:
1. Comment out the lines that strip docs from makepkg.
2. Run makeworld to rebuild packages.
I am still a little unsure how makeworld works. There is no man page. But you can get some info by running "makeworld --help" as follows:
bash-3.1$ makeworld --help
makeworld version 2.9.7
usage: /usr/bin/makeworld [options] <destdir> <category> [category] ...
options:
-b, --builddeps Build missing dependencies from source
-c, --clean Clean up work files after build
-d, --nodeps Skip all dependency checks
-f, --force Overwrite existing packages
-i, --install Install package after successful build
-h, --help This help
-r, --rmdeps Remove installed dependencies after a successful build
-s, --syncdeps Install missing dependencies with pacman
-S, --sudosync Install missing dependencies with pacman and sudo
where <category> is one or more directory names under the FST root
eg: makeworld -c /packages base lib editors
this should be run from the toplevel directory of FST (usually /var/fst)
bash-3.1$
I don't understand the -r, -s options.
Does makeworld automatically download and install all missing dependencies for a build? Or do you have to tell it to do so with -s or -S options.
How does the -r option work?
Rob

If you're building on a really clean (ie, not many packages) system, then most packages will fail to build, erroring out with a "missing dependencies" error. The -s/-S option will take care of this for you, and the -r option will clean up afterwards, if you so choose.

Similar Messages

Pacman -Syu after a major makeworld

so its like this a made a makewordl to oficcial an unoficcial packages
them one day e made pacman -Syu just in case new stuf appeared
after its finishes it askes if i want to upgrade some pakages e say Y
but its stops the upgrade . the error is something like
xcdroast exists in filesistem it shows the full patch but im to lazy to rigth it all .
did i do something wrong ?? can i fix it ? thanks

when did did you do this upgrade?
does this error still occur?
i had not realized that xcdroast had appeared in the unofficial tree twice so i removed one of the enteries. you may have been accessing the unofficial tree at this time.

N00b question about the ABS

Hey, I am new to Arch and I'm about to install it on my machine (used it a bit in a virtual machine) and I have a small nooby question about the ABS.
According to the wiki: https://wiki.archlinux.org/index.php/Arch_Build_System
"Running abs as root creates the ABS tree by synchronizing with the Arch Linux server."
Does this mean that the ABS tree (not the package) is always downloaded from the official Arch Linux servers, never from any of the mirrors?

jomasti wrote:
ANOKNUSA wrote:makepkg is part of the abs package.
You might be confusing that with makeworld. makepkg is included with pacman.
Anyway, gregor, you are confusing the AUR with ABS. Although, what you are saying is still possible via the source files when looking up a package on https://www.archlinux.org/packages/. But with both, using a program or using the respective page is a personal choice.
Yup, you're right. My mistake.

Pacman is broken. Yay.

Well, I wish I could give more info, but I haven't used arch for awhile now since pacman broke to the point it's not even recognized as a system command. It all started when I upgraded pacman. Probably been over a month. I can't remember. I do know the install gave errors about two files missing. Can't remember how to look back at the system log. I'd like to think I could just reinstall the previous pacman, but I'm kinda lost on how to do this considering the database only carries the latest version, which my kernel is apparently incompatible with (SCSI). Just a guess, of course.

pacman-2.9.6
pacman-2.9.6/doc
pacman-2.9.6/doc/makepkg.8.in
pacman-2.9.6/doc/pacman.8.in
pacman-2.9.6/COPYING
pacman-2.9.6/ChangeLog
pacman-2.9.6/Makefile.in
pacman-2.9.6/README
pacman-2.9.6/acconfig.h
pacman-2.9.6/config.guess
pacman-2.9.6/config.h.in
pacman-2.9.6/config.sub
pacman-2.9.6/configure
pacman-2.9.6/configure.in
pacman-2.9.6/install-sh
pacman-2.9.6/etc
pacman-2.9.6/etc/makepkg.conf
pacman-2.9.6/etc/pacman.conf
pacman-2.9.6/libftp
pacman-2.9.6/libftp/Makefile
pacman-2.9.6/libftp/ftplib.c
pacman-2.9.6/libftp/ftplib.h
pacman-2.9.6/scripts
pacman-2.9.6/scripts/gensync
pacman-2.9.6/scripts/makepkg
pacman-2.9.6/scripts/makeworld
pacman-2.9.6/scripts/pacman-optimize
pacman-2.9.6/scripts/updatesync
pacman-2.9.6/src
pacman-2.9.6/src/convertdb.c
pacman-2.9.6/src/db.c
pacman-2.9.6/src/db.h
pacman-2.9.6/src/list.c
pacman-2.9.6/src/list.h
pacman-2.9.6/src/md5.c
pacman-2.9.6/src/md5.h
pacman-2.9.6/src/md5driver.c
pacman-2.9.6/src/pacconf.h
pacman-2.9.6/src/package.c
pacman-2.9.6/src/package.h
pacman-2.9.6/src/pacman.c
pacman-2.9.6/src/pacman.h
pacman-2.9.6/src/pacsync.c
pacman-2.9.6/src/pacsync.h
pacman-2.9.6/src/rpmvercmp.c
pacman-2.9.6/src/rpmvercmp.h
pacman-2.9.6/src/strhash.c
pacman-2.9.6/src/strhash.h
pacman-2.9.6/src/util.c
pacman-2.9.6/src/util.h
pacman-2.9.6/src/vercmp.c
There's no output for "echo $PATH"
ls /var/lib/pacman lists my repository directories

Makemyworld

I have abs. I want to rebuild all my packages; not the whole world, just MY world (the ones I've installed), so I can apply my preferred compiler optimizations. Can makeworld do that?
I built one by hand (proftpd). Then I ran pacman on the full package name to install it. That worked. But I don't want to make every package by hand.
Seems if I had a script to makemyworld, it would be easiest to leave the pkg.tar.gz files right where they are created, just like when I built proftpd by hand. OTOH, it looks like gensync wants to see them all in one directory, is that correct?
I've only been using arch for a short time, so maybe I'm overlooking the obvious. Can anybody point me in the right direction?

In the User Contributions section, people have posted at least one, maybe two, scripts like that. Read through the history.

Creating optimized packages for my machine?

Well, I want to create x86-64 packages for my machine with Arch linux. I really enjoy pacman hence my decision.
Is there anything I need to do special for changing the optimization from i686 to x86-64? Or would a standard pkgbuild do this for me?
I read the documentation for making my own packages but I saw no way to change the optimizations that the package is built with. Does it rely on other files for the optimizations or is there a file I need to edit. I really have no clue as what I need to do exactly to make this happen.
The general build scripts seem pretty straight forward so I see no problem except for the optimization part. Any info is greatly appreciated, thanks.

sarah31 wrote:[...]you would need a PPC first.[...]
well, that's the only problem i have ... the hardware looks much nicer!! i would really like to have a white laptop instead of a black one (thinkpad -> good hardware, flexiview-screen, but black is somewhat uncool) --- but when i find a cheap powerbook (students do not have a lot of money ), i will definitely makeworld from arch-things --- this means actually: if i come to a powerbook of at least 800MHz, i will start a ArchPowerPC project, if Judd likes this idea of me using his pacman/makepkg to build an arch for PPC's
... but it may take at least time till may, because i have a lot of exams in next months :-)

Mesa 7.0.3 build fails

Hey everyone,
Recently I acquired a new system and installed arch on it (as a linux-only gaming box), and built everything from the ground up using makeworld at first and then building my necessary packages (minimal X install and libs, etc). However I've run into a little problem while trying to build mesa from the main ABS tree.
Here is what happens during the compile:
make[2]: Leaving directory `/var/abs/extra/mesa/src/Mesa-7.0.3/src/glw'
make[1]: Leaving directory `/var/abs/extra/mesa/src/Mesa-7.0.3/src'
make[1]: Entering directory `/var/abs/extra/mesa/src/Mesa-7.0.3/progs'
make[1]: Nothing to be done for `install'.
make[1]: Leaving directory `/var/abs/extra/mesa/src/Mesa-7.0.3/progs'
gcc -march=native -mtune=generic -O2 -pipe -I/var/abs/extra/mesa/pkg/usr/include -I../../include glxinfo.c -L../../lib -L../../lib64 -lGL -lGLU -o glxinfo
gcc -march=native -mtune=generic -O2 -pipe -I/var/abs/extra/mesa/pkg/usr/include glxgears.c -lGL -o glxgears
/tmp/cc8iuPJg.o: In function `gear':
glxgears.c:(.text+0x11c): undefined reference to `sincos'
glxgears.c:(.text+0x1ed): undefined reference to `sincos'
glxgears.c:(.text+0x2b8): undefined reference to `sincos'
glxgears.c:(.text+0x2fc): undefined reference to `sincos'
glxgears.c:(.text+0x340): undefined reference to `sincos'
/tmp/cc8iuPJg.o:glxgears.c:(.text+0x384): more undefined references to `sincos' follow
/tmp/cc8iuPJg.o: In function `gear':
glxgears.c:(.text+0x735): undefined reference to `sincosf'
glxgears.c:(.text+0x757): undefined reference to `sincos'
glxgears.c:(.text+0x7e3): undefined reference to `sincos'
glxgears.c:(.text+0x8d9): undefined reference to `sincos'
glxgears.c:(.text+0x950): undefined reference to `sincos'
glxgears.c:(.text+0xaae): undefined reference to `sincosf'
glxgears.c:(.text+0xadf): undefined reference to `sincos'
collect2: ld returned 1 exit status
make: *** [glxgears] Error 1
make: *** Waiting for unfinished jobs....
==> ERROR: Build Failed.
Aborting...
I'm building mesa on a completely fresh system, and doing so exclusively using ABS/makepkg from the main abs tree - I don't know what I'm doing wrong. Your help would be appreciated
Thanks

@Snowman, thanks for the response. Unfortunately, I tried your suggestion and tried to build the package from the PKGBUILD but it still does not build - it stops compiling at the very same place as it originally stopped.

Maintaining arch src code for offline compilations/hacking

hello,
i would like to maintain local copy of all pkgbuilds and associated tarballs, patches, and what not that is needed to build a package. my main catalyst behind this is that i do not always have an internet connection and i find myself need to recompile a package or just would like to have available src code for offline viewability. to my knowledge archlinux does not have src ISOs.
i looked into the manpages and '--allsource' switch for makepkg along with 'makeworld' could be leveraged to accomplish what i'm trying to do. they only thing i'm worried about is if the combination of these commands can be used to perform incremental syncs monthly to maintain fresh copy of archlinux source code,
any help and guidance is appreciated, thanks

jasonwryan wrote:Have you looked at asp?
looks like a pretty neat tool over abs, but it doesn't seem to interpret PKGBUILD files to fetch the needed tarballs etc like makepkg would do.
for now i copied /var/abs to ~/ and i cd into {core,extra,..} and use this:
for d in *; do cd $d; makepkg --allsource --verifysource -f; cd ..; done

A64 optimization package building?

Well, I Have started to mess with A64 flags in the makepkg.conf file. For my first compile I decided to use Red_over_Blue's aterm example. Since this was my first attempt at a package I just wanted to see if it worked properly. So I did the pacman -A aterm-0.4.2-4.pkg.tar.gz
It worked flawlessly, but, it left me with a few questions.
Since I am compiling for A64 style cpu why when I pacman it and then run the aterm it worked without issues? Arch by default and my system is i686 currently. The package I built should be A64 only shouldn't it?
Here is my makepkg.conf settings that I used.
export CARCH="k8"
export CHOST="k8-pc-linux-gnu"
export CFLAGS="-march=k8 -02 -pipe"
export CXXFLAGS="-march=k8 -02 -pipe"
I am not sure if I was supposed to change the CARCH and CHOST options. I looked at the options they were using on gentoo and found -march=k8 is the default for A64 style cpu's.
So the question is, is my package true A64? Or is it just optimized but for 32bit? If I missed something here what do I do for a true A64 setup?
Any input is good input thanks for any replies.

you have no issues with it, because your cpu supports i686 and k8
if e.g. i would try your pkg, it would not work at all --- because my cpu do not support the commands the binary will give to it
if you only made one pkg, then your system is mostly running i686 and only this pkg is possible to run k8 --- what you need to do is a makeworld of all pkgs you want ... this can give big trouble, because of e.g. gcc and others
good luck

How to rebuild entire system using ABS

ArchLinux ABS Wiki says:
The Arch Build System (ABS for short) is used to:
* Rebuild your entire system using your compiler flags, "a la FreeBSD"
But how? I was looking for a wiki, an article or example - no results Please explain, how to rebuild entire system using ABS?
Thanks in advance for your help!
Last edited by rics (2008-08-21 13:25:03)

Allan wrote:makeworld script in the abs package
So easy?! Cool!
Thanks! My problem is solved

X, Schmex

Yesterday, I posted a message here concerning an error I was getting concerning module dependencies. Since I have built in everything and there are no modules the file sought by /etc/rc.sysinit hadn't been created as typically it would. I edited /etc/rc.sysinit commenting out the superfluous lines. Now fine, I went on to rebuild the base packages using makeworld, a story in itself, and later makepkg to compile Xfree86, openbox, and aterm. I configured X with the aging xfree86config, doing it the way I've done it countless times. At reboot I noticed that I was getting the same old module dependency message I'd managed to put out of its misery yesterday. I checked and sure enough the file had been overwritten by some process, almost certainly during the installation of xfree86, so I edited it again.
That fixed, I went on to running startx. Sadly, it brings output:
(EE) xf86OpenSerial: cannot open device /dev/mouse
No such file or directory
(EE) Mouse1: cannot open input device
(EE) PreInit failed for input device: "Mouse1"
No core pointer
Fatal server error:
failed to initialize core devices
Clearly, there is a problem here with the mouse. Why I can imagine. Could this be a kernel problem with a possible need to reconfigure and recompile? If it is, what proceedure, if any, is recommended with Arch for doing a reconfiguration?
jlowell

Hi Sarah!
You'll find /etc/X11/XF86Config below:
# File generated by xf86config.
# Copyright (c) 1999 by The XFree86 Project, Inc.
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
# Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
# FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/misc/psaux"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31-70
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 55-120
EndSection
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "** Matrox Graphics (generic) [mga]"
Driver "mga"
#VideoRam 32768
# Option "mga_sdram"
# Insert Clocks lines here if appropriate
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "** Matrox Graphics (generic) [mga]"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "800x600"
ViewPort 0 0
EndSubsection
EndSection
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
You know, I wonder if this problem may have some relation to xfs not starting at boot. While I'm told that the latest versions of xfree86 don't require xfs to start at boot, I wonder if it couldn't hurt trying to turn it on.
I'll look forward to hearing from you.
jlowell

Arch Idea's, perhaps...

Hi, I've been sitting around today and doing a little bit of day dreaming about some idea's that I think would be helpful to this community and to ArchLinuc as well.
One question first... a little off topic but here goes anyway: What language is pacman coded with, bash? I didn't bother to look myself....yet. Thought I'd ask while I was here.
And now back to the show.
I've been on and off of arch for sometime now and have realized something. It has this strange affect on me... much like that slackware affect you get where you just love the distro but you don't really know why exactly. It's that feeling you just can't put your finger on and it feel's all warm and toasty inside. But most important and noticeable of all, whenever you try out another distro you find yourself always coming back to your one true love.
So by now I've scared everyone off with my useless rantings, but wait a second here... is that what i think it is?.... Oh! People are still reading !
As I was saying, and before I get WAY too off topic I have this urge to develope some useful tools for ArchLinux to sort of make everyday things easier. But what I'm really curious about is wheither or not anyone has any suggestions or ideas they would like to share.
Basically just give me some ideas off the top of your head that you would see or like to see made possible, wheither it be tools, programs, and even eye candy (arch specific of course ).
Anyway, sorry for the obvious derailed train wreck of a question here, I'm just all over the place today.

p0indext0r wrote:Basically just give me some ideas off the top of your head that you would see or like to see made possible, wheither it be tools, programs, and even eye candy (arch specific of course ).
Well, this probably is not what you want to hear, but I only have one aching (arching? ) need for Arch: documentation. More documentation. Better documentation. Mo' betta docs.
I'm still practicing using the Arch-specific tools that already exist, never mind figuring out how to use various Linux apps on my Arch Linux installation. ATM, I don't need new ones. What would be most helpful is more discursive docs, examples, even exercises. Like most man pages, man pacman and man makepkg are informative, but they aren't particularly instructive.
This is a nice example of "instructive":
http://wiki.archlinux.org/index.php/Alsa%20setup
That's what I think Arch needs more of, especially with regard to the kinds of issues and tasks associated with pacman/makepkg, and even makeworld (which is way beyond my comprehension ATM). For example, from man makepkg:
Notice that the "/usr" portion should be present with "prefix", but not "DESTDIR". "DESTDIR" is the favorable option to use, but not all Makefiles support it. Use "prefix" only when "DESTDIR" is unavailable.
Ok. How do I know when "DESTDIR" is unavailable? I made a PKGBUILD for WMxmms. It works, not quite like I expected but it functions. I tried to follow various PKGBUILDs for other WM dock apps as a guide, but even these are all over the map. Some use "DESTDIR," some use "prefix." Some that use "DESTDIR" still have "/usr" present. I don't get that.
Here is another example, from Crux, of what I think Arch needs more of:
http://crux.fh-regensburg.de/cgi-bin/cv … GnomePorts
The nice thing here is that it is distro-specific -- i.e., it tells you a Crux way of installing Gnome -- and goal-oriented, as well as instructive. It's set-up in an "if you want/use ..., then you need ..." format. It preserves the freedom of choice that Crux (and Arch) users value. You can adapt it to your needs, rather than just installing something pre-configured, and most importantly, you can learn from it.
For me, these are the kinds of things that would make everyday things easier.

Lowarch 0.1.1 (Savitri) - i486 Arch based Distro - Released

I needed to make a new release now, since the current repo address has changed, so the old install cd and floppies don't work for ftp install anymore (without changing the url, of course).
But there are of course package upgrades and bug fixes as well. And now all the install floppies are finished. There's also the ongoing process of deleting unimportant packages and adding new useful ones.
Quite a few people have joined and done some very useful testing. I'm always happy to hear about problems and other experiences with different systems (old and new). So give it a try if you have some free disk space, time and think it's fun.

cr7 wrote:when I need to customize my rc.conf, I have to set the keymap as "i386/qwerty/it.map.gz", instead of "it_IT" as in Arch Linux.
Shouldn't it be just 'it', not it_IT? I thought it_IT is for locale. I use 'no' (Norwegian) without problems.
cr7 wrote:If I want to recompile the entire system for i586, with updated packages, how can I do? :?:
I'm running lowarch on a Pentium M, and I can't say I have noticed any difference in speed between Arch and Lowarch on it. I doubt you will see any difference at all with the system compiled for i586 instead of i486.
But if you think it's fun to try out things, here's how:
Download http://www.lowarch.org/abs.tar.bz2 which is the current abs tree. (I don't have access to cvs server or similar, so I can't set up normal abs access.
Change the /etc/makepkg.conf
Extract the abs.tar.gz (it'll be called abs-clean because my abs tree has all the source files, so I have a script copying all the files except source files to abs-clean)
in the abs-clean directory use makeworld to build all the packages.
(On the 166Mhz It will last, oh, about, let's see /me is calculating ....ahh about an eternity...) If you'll use a i686 machine for the compiling, you should install lowarch on it, and use the uname hack (search for it, I don't have the link in my head, if you don't find it, tell me).
Then use gensync to create a custom repo of the files.

Compiling a few apps at once: XFCE4 CVS

Hello. I'm trying to write a single PKGBUILD to create the XFCE4 CVS version, but I've got a few problems. A lot of packages in XFCE4 depend on other packages in XFCE4. I'd like to install one package into $startdir/pkg and then I want to make the configure scripts of the other packages to find the app installed in $startdir/pkg and use it. However, I've no idea how to achieve this.
Can anyone give me a hand?

sweiss wrote:
Thing is, this is a CVS version. Much easier to maintain for something that is updated every other night, at least for testing purposes.
As for the URL, I know how to build XFCE4 basically, I've already coded a program to generate every PKGBUILD for a given package name, grouping them all under xfce4-cvs. But I'd like to make it into one PKGBUILD as I find it easier for me to maintain until XFCE stabilizes.
Also, it's a rather educational question, for my general knowledge. Can you tell me how to achieve this?
technically it is possible to hack build() to use more $startdirs and then make pkgs for each, but in my eyes it is nonsense, as the principle for a PKGBUILD is to make one pkg --- what you want i think is done with "makeworld" (see docs) that runs makepkg in a directory on each PKGBUILD in a subdir
also if you would hack the build() and do invest a lot of time: the trouble that will come up is: libSOMETHING is often a dependency to SOMETHINGELSE, and therefore you cannot build them in one pkg (as the libSOMETHING must first be installed before you can compile something against it) --- if you want to save you time, make a local repository (see docs) and add xfce4-cvs to it and then when you run makeworld in this directory, it will build you the pkgs - then "gensync" and then (when the local repo is in pacman.conf), the next time you run pacman -Suy, it will ask you to update your xfce4-cvs pkgs, as in your local repo, they are updated [this as an alternative to pacman -U pkgname.pkg.tar.gz for every pkg that can be boring]

Rebuild the whole system?

I've been quite amazed, but I really couldn't find any way of rebuilding my whole system with this famous ABS. The strange thing about it is, that I read in the docs, that it is possible with one command :?
So - is it possible, or not? Do I have to play a lot with makeworld or srcpac?
PS. Okay, I am used to Gentoo, so what?

josolanes wrote:
Benol wrote:
http://www.archlinux.org/docs/en/guide/install/arch-install-guide.html wrote:This is backed by an easy-to-use binary package system that allows you to upgrade your entire system with one command. Arch also uses a ports-like package build system (Arch Build System) to make it easy to build packages, which can also be synchronized with one command. Oh yeah, and you can rebuild your entire system with one command, too. Everything is done quite simply and transparently.
How's that?
So the RIGHT method to get software is "pacman -S foo". If I want to compile then I have to go to /var/abs/boo/foo and "makepkg -i"? Why isn't it described detailed anywhere?
hmm...the only thing i have under /var/abs/ is /var/abs/local/ (which is empty btw) and the log file.
is this because i cleared the cache in the past?
if so, is there a way to rebuild the system still?
pacman -S cvsup
abs
to get the PKGBUILDS in /var/abs
/etc/abs/abs.conf to configure abs

Makeworld

Similar Messages

Maybe you are looking for