-=-=--
DrakX is a very big project, and it needs special setups to work.
The purpose of this file is to explain how you can setup your box to make it
compile and run.
-=-=--
Beware, don't try this on a production machine with important data.
--------------------------------------------------------------------------
Sources installation:
First grab the gi.tar.bz2 archive and untar it in your home directory,
for example from DrakX-*.src.rpm on your Mandrake Linux distribution.
cd to gi
for i in `du -a | grep CVS/Root | cut -f 2`
do
sed -e 's/prigaux/anoncvs/' $i > $i.tmp
mv $i.tmp $i
done
Then, log yourself into the cvs:
% export CVS_RSH=ssh
% export CVSROOT=:ext:anoncvs@cvs.mandrakesoft.com:/cooker
% cvs checkout gi
(passwd: 'cvs')
And update the gi package:
cvs update -P -d
--------------------------------------------------------------------------
Preparing the compilation process:
(1) target directory
create a /export directory and copy a recent Mandrake Linux CD in there.
(You don't have to put have all the RPMS...) ; you'll need roughly 1.5
Gbytes for a full install.
[gc@obiwan ~/cvs/gi] su -c "mkdir /export"
(2) devel packages
you need quite a few devel packages to run the stuff; roughly: gcc, make,
glibc-devel, perl-devel, XFree86-devel, libglib-devel, libgtk+-devel,
perl-GTK, ldetect*, libslang-devel, libnewt-devel, e2fsprogs, dosfstools,
rpm-devel, popt-devel, rpmtools, libbzip2*, libncurses*.
you may need a few others I forgot to mention. if the compilation
fails, try to understand the message and install any necessary
remaining package.
(3) sudo
never build or run DrakX as root; install package sudo, and set up
relevant permissions; the following should be enough: (in your
/etc/sudoers)
gc ALL=(root) NOPASSWD:/usr/bin/patch,NOPASSWD:/bin/rpm,NOPASSWD:/bin/mount,NOPASSWD:/bin/cp,NOPASSWD:/bin/umount,NOPASSWD:/usr/bin/install,NOPASSWD:/bin/rm,NOPASSWD:/bin/mv,NOPASSWD:/bin/tar,NOPASSWD:/bin/cpio,NOPASSWD:/bin/chown,NOPASSWD:/bin/mkdir,NOPASSWD:/usr/bin/strip,NOPASSWD:/bin/mknod
(4) boot kernel
you need one or more kernels and (all?) their modules. it's located in
subdirectory "all.kernels" in DrakX-*.src.rpm ; if you ever grab (or
build) another boot kernel, replace or add an entry in "all.kernels" as:
(a) create your modules subdir (useful to describe the
VERSION_RELEASE) and untar your kernel
[gc@obiwan ~/cvs/gi/all.kernels] mkdir 2.4.1-BOOTcustom
[gc@obiwan ~/cvs/gi/all.kernels] cd 2.4.1-BOOTcustom
[gc@obiwan ~/cvs/gi/all.kernels/2.4.1-BOOTcustom] tar jxvf ~/mycustomkernel.tar.bz2
[gc@obiwan ~/cvs/gi/all.kernels/2.4.1-BOOTcustom] ls
boot/ cardmgr/ lib/
(c) build kernel/modules stuff for stage1 and stage2
[gc@obiwan ~/cvs/gi] ./update_kernel
(5) pray
[gc@obiwan ~/cvs/gi] make
---------------------------------------------------------------------------
The comments written with #- are automatically stripped out at install.
---------------------------------------------------------------------------
testing all:
go to the perl-install directory and execute ./g_auto_install --test
You should be able to test the whole thing in a non-destructive way.
NEVER compile and/or execute DrakX as root!
Here is how I (dams) made it work on my computer.
-------------------------------------------------
- get the sources
- install the librairies needed included newt-devel gtk+-devel popt-devel popt gtk-engines
- cd path/to/gi
- make
- mkdir /usr/share/gtk
- ln -s path/to/gi/perl-install/share/themes /usr/share/gtk
- ln -s path/to/gi/perl-install/share/step-* /usr/share
- ln -s path/to/gi/perl-install/share/help.xpm /usr/share
- ln -s path/to/gi/perl-install/share/isdn* /etc/sysconfdir/network-scripts
- have a cd architecture linked on /export
- ln -s /export /tmp/rhimage
- export PERL_INSTALL_TEST=1
- cd path/to/gi/perl-install
- gendistrib --noclean --distrib /export
- ./install2 in root (dangerous) or chmod a+r /dev/hd* and ./install2 in user
address all bugreports to dave@null.com
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qt3-devel%20needed%20for%20Trinitydesktop%20%28KDE%203.5%0A%09successor%29&In-Reply-To=%3Cm3hbate9mc.fsf%40blino.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003551.html">
<LINK REL="Next" HREF="003554.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)</H1>
<B>Olivier Blin</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qt3-devel%20needed%20for%20Trinitydesktop%20%28KDE%203.5%0A%09successor%29&In-Reply-To=%3Cm3hbate9mc.fsf%40blino.org%3E"
TITLE="[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)">mageia at blino.org
</A><BR>
<I>Wed Mar 23 23:48:43 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003551.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI>Next message: <A HREF="003554.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3553">[ date ]</a>
<a href="thread.html#3553">[ thread ]</a>
<a href="subject.html#3553">[ subject ]</a>
<a href="author.html#3553">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> writes:
><i> We shouldn't under any circumstances add kde3 in the repos, fork or not.
</I>><i>
</I>><i> Users see a package in the repos and they expect it to be maintained,
</I>><i> this will not be the case, we can't support KDE4 and KDE3 at the same
</I>><i> time. Past experience tells us this is a major hassle/pain, and we
</I>><i> shouldn't have to go back to that murky situation.
</I>
That's not KDE3, it's a fork with new maintainers.
><i> Also there shouldn't be any qt3 dependant packages in the repos; the
</I>><i> only and sole reason qt3 is in the Mageia repos is that stewbintn said
</I>><i> he needs it for some LSB stuff, but nothing is built with qt3-devel as
</I>><i> BR AFAIK and nothing should be.
</I>
It should be ok to add back qt3-devel temporarily, and remove it again
once Trinity gets ported to Qt4.
--
Olivier Blin - blino
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003551.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI>Next message: <A HREF="003554.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3553">[ date ]</a>
<a href="thread.html#3553">[ thread ]</a>
<a href="subject.html#3553">[ subject ]</a>
<a href="author.html#3553">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|