Le samedi 07 mai 2011 à 23:46 -0400, Jasper St. Pierre a écrit :
But this approach only goes so far: there's eventually going to be a
point where you'll need a newer polkit or networkmanager version, and
whoops, those need to run those as root.
That said, I think jhbuild is a convenient way of
On Sat, 2011-05-07 at 18:53 -0700, bsquared wrote:
Tshepang Lekhonkhobe wrote:
I would use that package manager of yours to remove jhbuild from the
system (uninstall_package jhbuild), and the re-run the confmakeinstall
commands. This is just a guess, and me hopes someone who understands
Jasper St. Pierre wrote:
You already did. jhbuild will install in whatever you specified as prefix.
[1]
The jhbuild instructions are for people who already have a proper gnome2
install and want to try out gnome3 easily safely: run a shell script,
jhbuild build, jhbuild run gnome-shell
Milan Bouchet-Valat wrote:
Le samedi 07 mai 2011 à 23:46 -0400, Jasper St. Pierre a écrit :
But this approach only goes so far: there's eventually going to be a
point where you'll need a newer polkit or networkmanager version, and
whoops, those need to run those as root.
That said, I think
Tshepang Lekhonkhobe wrote:
I would use /opt as jhbuild prefix and see how things churn out. Also,
the only first-class jhbuild target is GNOME 3, meaning that Xorg
support might be broken even, so you might have to follow BLFS Xorg
instructions for it. But try the jhbuild way first, and report
On Sun, 2011-05-08 at 10:38 -0700, bsquared wrote:
Tshepang Lekhonkhobe wrote:
I would use /opt as jhbuild prefix and see how things churn out. Also,
the only first-class jhbuild target is GNOME 3, meaning that Xorg
support might be broken even, so you might have to follow BLFS Xorg
Tshepang Lekhonkhobe wrote:
Me too, but why not make an exception with jhbuild software. You already
made an exception by breaking the guidelines of your package management
system: according to it, each package must have its own package user,
but with jhbuild, stuff built all have jhbuild as
On Fri, 2011-05-06 at 16:02 -0700, bsquared wrote:
I have installed jhbuild in a basic LFS environment using standard build
tools: configure --prefix=/usr ; make make install. files[1] are
installed to /usr. But modulsets dir remained with source, so I copied
to user dir /usr/src/jhbuild
Tshepang Lekhonkhobe wrote:
On Fri, 2011-05-06 at 16:02 -0700, bsquared wrote:
I have installed jhbuild in a basic LFS environment using standard build
tools: configure --prefix=/usr ; make make install. files[1] are
installed to /usr. But modulsets dir remained with source, so I copied
to
On Sat, 2011-05-07 at 10:05 -0700, bsquared wrote:
Tshepang Lekhonkhobe wrote:
On Fri, 2011-05-06 at 16:02 -0700, bsquared wrote:
I have installed jhbuild in a basic LFS environment using standard build
tools: configure --prefix=/usr ; make make install. files[1] are
installed to /usr.
Tshepang Lekhonkhobe wrote:
Interesting approach there.
Does that make sense? Is it possible?
Have you tried using './configure --prefix=/usr --sysconfdir=/etc' for
jhbuild?
That was a good suggestion. I should have though of that myself, but no
go. After './comfigure ; make make
jhbuild is not a general purpose build system for building gnome. It's
designed to sandbox a gnome setup and keep anything from interacting with
it... like a chroot, but more usable.
The prefix variable defines where things like bin, lib and etc go.
Because of the sandbox aspect, setting your
Jasper St. Pierre wrote:
jhbuild is not a general purpose build system for building gnome. It's
designed to sandbox a gnome setup and keep anything from interacting with
it... like a chroot, but more usable.
The prefix variable defines where things like bin, lib and etc go.
Because of the
On Sat, 2011-05-07 at 14:23 -0700, bsquared wrote:
Tshepang Lekhonkhobe wrote:
Interesting approach there.
Does that make sense? Is it possible?
Have you tried using './configure --prefix=/usr --sysconfdir=/etc' for
jhbuild?
That was a good suggestion. I should have though of
Tshepang Lekhonkhobe wrote:
I would use that package manager of yours to remove jhbuild from the
system (uninstall_package jhbuild), and the re-run the confmakeinstall
commands. This is just a guess, and me hopes someone who understands
this technology (can one specify sysconfdir to /etc?) will
Jasper St. Pierre wrote:
jhbuild is not a general purpose build system for building gnome. It's
designed to sandbox a gnome setup and keep anything from interacting with
it... like a chroot, but more usable.
The prefix variable defines where things like bin, lib and etc go.
Because of the
You already did. jhbuild will install in whatever you specified as prefix.
The jhbuild instructions are for people who already have a proper gnome2
install and want to try out gnome3 easily safely: run a shell script,
jhbuild build, jhbuild run gnome-shell --replace. There's no chance that
I have installed jhbuild in a basic LFS environment using standard build
tools: configure --prefix=/usr ; make make install. files[1] are
installed to /usr. But modulsets dir remained with source, so I copied
to user dir /usr/src/jhbuild (jhbuild user's home). I changed
modulesets_dir =
You need write access to whatever you assign to 'prefix'.
On Fri, May 6, 2011 at 7:02 PM, bsquared bwcod...@gmail.com wrote:
I have installed jhbuild in a basic LFS environment using standard build
tools: configure --prefix=/usr ; make make install. files[1] are
installed to /usr. But
19 matches
Mail list logo
