Or, you could point emerge directly to the ebuild.
# emerge bar-misc/bender/bender-4.0.ebuild
If bender 4.0 is ~arch it will still install it, however it won't
attempt to install any other ~arch stuff.
Max.
> Here's what you do: Let's say bender has the following dependencies, as
> reported by
Or, you could point emerge directly to the ebuild.
(I don't know why we're using 'bender', but I will continue with it)
# emerge bar-misc/bender/bender-4.0.ebuild
If bender 4.0 is ~arch it will still install it, however it won't
attempt to install any other ~arch stuff.
Max.
On Tue, 2004-01-1
On Tue, 2004-01-13 at 02:34, Thomas T. Veldhouse wrote:
> If blender were to have a lot of dependencies, how would you keep the ~x86
> versions from being installed (assuming blender would run with the x86
> versions)?
Here's what you do: Let's say bender has the following dependencies, as
reporte
On Mon, 2004-01-12 at 16:38, Thomas T. Veldhouse wrote:
> No, my concern is that a bunch of system packages may be upgraded as well to
> "testing" version when doing this (maybe not for blender, but when using
> ACCEPT_KEYWORDS="~x86"). I don't want the compiler, gettext, autoconf or
> anything el
On Mon, 2004-01-12 at 10:38, Thomas T. Veldhouse wrote:
> No, my concern is that a bunch of system packages may be upgraded as well to
> "testing" version when doing this (maybe not for blender, but when using
> ACCEPT_KEYWORDS="~x86"). I don't want the compiler, gettext, autoconf or
> anything el
Thomas T. Veldhouse said:
> my concern is that a bunch of system packages may be upgraded
> as well to "testing" version when doing this (maybe not for
> blender, but when using ACCEPT_KEYWORDS="~x86").
Use -p to see what it will upgrade.
-Eric
--
arctic bears - email and name services
25 email
David Gethings wrote:
> On Mon, 2004-01-12 at 16:04, Thomas T. Veldhouse wrote:
>> If blender were to have a lot of dependencies, how would you keep
>> the ~x86 versions from being installed (assuming blender would run
>> with the x86 versions)?
> If I understand your correctly; installing with ~x8
On Mon, 2004-01-12 at 16:04, Thomas T. Veldhouse wrote:
> If blender were to have a lot of dependencies, how would you keep the ~x86
> versions from being installed (assuming blender would run with the x86
> versions)?
If I understand your correctly; installing with ~x86 will only pull in
the neces
Simon Prosser wrote:
> On Sunday 11 January 2004 4:40 pm, Thomas Degris wrote:
>> My question: what do I have to do to get the ebuild of the version
>> 2.31 of Blender ?
> ACCEPT_KEYWORDS="~x86" emerge blender -pv
If blender were to have a lot of dependencies, how would you keep the ~x86
versions
Thanks, very handy and usefull indeed.
Thomas
Andrew Cowie wrote:
On Mon, 2004-01-12 at 04:10, Thomas Degris wrote:
Thanks, why didn't I get this package by emerge -s blender ?
I use etcat for this sort of thing. It's in gentoolkit.
procyon:~ # qpkg -f /usr/bin/etcat
app-portage/gentool
On Mon, 2004-01-12 at 04:10, Thomas Degris wrote:
> Thanks, why didn't I get this package by emerge -s blender ?
I use etcat for this sort of thing. It's in gentoolkit.
procyon:~ # qpkg -f /usr/bin/etcat
app-portage/gentoolkit *
procyon:~ #
Do this yourself at home - it's really impressive in fu
then what's kind of package is blender-2.31a because:
[EMAIL PROTECTED] emerge -s crystalspace
Searching...
[ Results for search key : crystalspace ]
[ Applications found : 2 ]
* dev-games/crystalspace
Latest version available: 20030413-r1
Latest version installed: 20030413-r1
Size
On Sunday 11 January 2004 5:40 pm, Thomas Degris wrote:
> Thanks, why didn't I get this package by emerge -s blender ?
because:=
[EMAIL PROTECTED] pross # ACCEPT_KEYWORDS="~x86" emerge -s blender
Searching...
[ Results for search key : blender ]
[ Applications found : 1 ]
* media-gfx/blender
Thanks, why didn't I get this package by emerge -s blender ?
Simon Prosser wrote:
On Sunday 11 January 2004 4:40 pm, Thomas Degris wrote:
My question: what do I have to do to get the ebuild of the version 2.31
of Blender ?
ACCEPT_KEYWORDS="~x86" emerge blender -pv
--
[EMAIL PROTECTED] ma
On Sun, Jan 11, 2004 at 05:40:41PM +0100, Thomas Degris wrote:
> My question: what do I have to do to get the ebuild of the version 2.31
> of Blender ?
>
Hiya,
Looking at my portage tree its already there. 2.28 will be marked as stable while
2.31 will be marked as unstable. Therefore to get t
On Sunday 11 January 2004 4:40 pm, Thomas Degris wrote:
> My question: what do I have to do to get the ebuild of the version 2.31
> of Blender ?
ACCEPT_KEYWORDS="~x86" emerge blender -pv
--
[EMAIL PROTECTED] mailing list
Hello,
the current Blender ebuild is for blender 2.28 and Blender is now at
version 2.31 (there is already a package in Debian Sid). So, I first
compiled Blender myself and it runs fine without any trouble. Then, I
decided to write an ebuild for that, so I started reading the
documentation from ge
Am Sonntag, 22. Juni 2003 02:28 schrieb Klaus D. Neumann:
> > > [EMAIL PROTECTED] klaus $ guessing 'blender' == '/usr/bin/blender'
> > > Xlib: extension "GLX" missing on display ":0.0".
> > > ERROR: Unable to open Blender window
> > >
> > > [2]+ Exit 1 blender
> > >
On Saturday 21 June 2003 04:23 pm, Mervin Bickerdyke wrote:
> Am Sonntag, 22. Juni 2003 01:09 schrieb Klaus D. Neumann:
> > Hi,
> >
> > after emerging blender 2.27, I tried to start it:
> > -
> > blender &
> > [2] 9905
> > [EMAIL PROTECTED] klaus $ guessing 'blender' == '/us
Am Sonntag, 22. Juni 2003 01:09 schrieb Klaus D. Neumann:
> Hi,
>
> after emerging blender 2.27, I tried to start it:
> -
> blender &
> [2] 9905
> [EMAIL PROTECTED] klaus $ guessing 'blender' == '/usr/bin/blender'
> Xlib: extension "GLX" missing on display ":0.0".
> ERROR:
Hi,
after emerging blender 2.27, I tried to start it:
-
blender &
[2] 9905
[EMAIL PROTECTED] klaus $ guessing 'blender' == '/usr/bin/blender'
Xlib: extension "GLX" missing on display ":0.0".
ERROR: Unable to open Blender window
[2]+ Exit 1 blender
--
21 matches
Mail list logo
