Am 01.02.2013 03:41, schrieb Philip Webb:
Firefox 17.0.2 requires alsa-lib , which I don't want as I don't use sound;
this is still the case with USE=-alsa.
I want to test what happens if I try to compile it without that dep,
so I copied the ebuild to
On Fri, 01 Feb 2013 10:07:24 +0100, Michael Hampicke wrote:
What about not using the local overlay and simply do emerge --nodeps
firefox and see what happens? I know, crude but simple :)
Because every emerge @world will want to install ALSA.
You may find it will not compile without
Neil Bothwick wrote:
On Fri, 01 Feb 2013 10:07:24 +0100, Michael Hampicke wrote:
What about not using the local overlay and simply do emerge --nodeps
firefox and see what happens? I know, crude but simple :)
Because every emerge @world will want to install ALSA.
SNIP
Don't add it to
On Fri, 01 Feb 2013 04:42:38 -0600, Dale wrote:
What about not using the local overlay and simply do emerge --nodeps
firefox and see what happens? I know, crude but simple :)
Because every emerge @world will want to install ALSA.
Don't add it to the world file then, just upgrade
Neil Bothwick wrote:
On Fri, 01 Feb 2013 04:42:38 -0600, Dale wrote:
What about not using the local overlay and simply do emerge --nodeps
firefox and see what happens? I know, crude but simple :)
Because every emerge @world will want to install ALSA.
Don't add it to the world file
2013/2/1 Neil Bothwick n...@digimed.co.uk
On Fri, 01 Feb 2013 10:07:24 +0100, Michael Hampicke wrote:
What about not using the local overlay and simply do emerge --nodeps
firefox and see what happens? I know, crude but simple :)
Because every emerge @world will want to install ALSA.
On Fri, 01 Feb 2013 05:35:06 -0600, Dale wrote:
Don't add it to the world file then, just upgrade it manually each
time.
Then portage will want to depclean it. It is always best to try to use
the methods portage provides instead of trying to be clever than it.
When you start working
Neil Bothwick wrote:
On Fri, 01 Feb 2013 05:35:06 -0600, Dale wrote:
Don't add it to the world file then, just upgrade it manually each
time.
Then portage will want to depclean it. It is always best to try to use
the methods portage provides instead of trying to be clever than it.
When
On Fri, 01 Feb 2013 06:59:43 -0600, Dale wrote:
work AROUND portage with a lot of things. This would include
depclean.
Which is why I think you shouldn't try to work around portage. It
provides a clean way of doing this, overlays, use them.
Then you have to update those too. As I
Neil Bothwick wrote:
On Fri, 01 Feb 2013 06:59:43 -0600, Dale wrote:
work AROUND portage with a lot of things. This would include
depclean.
Which is why I think you shouldn't try to work around portage. It
provides a clean way of doing this, overlays, use them.
Then you have to update
On Fri, 01 Feb 2013 07:32:24 -0600, Dale wrote:
Then you have to update those too. As I said, either way in the long
term, you have to work at overriding portage defaults.
But an overlay is working with portage, the other options are trying
to trick it.
I'm not saying it is. I'm
130201 Michael Hampicke wrote:
What about not using the local overlay
and simply do 'emerge --nodeps firefox' and see what happens?
Philip wants to find out if he can compile FF without alsa-lib.
To just test this case, 'emerge --nodeps ff' is perfect.
If he finds out that ff would infact
Firefox 17.0.2 requires alsa-lib , which I don't want as I don't use sound;
this is still the case with USE=-alsa.
I want to test what happens if I try to compile it without that dep,
so I copied the ebuild to /var/lib/layman/local/www-client/firefox/
commented the relevant line to remove the
On 1/31/2013 20:41, Philip Webb wrote:
Firefox 17.0.2 requires alsa-lib , which I don't want as I don't use sound;
this is still the case with USE=-alsa.
I want to test what happens if I try to compile it without that dep,
so I copied the ebuild to /var/lib/layman/local/www-client/firefox/
130131 Dustin C. Hatch wrote:
On 1/31/2013 20:41, Philip Webb wrote:
Firefox 17.0.2 requires alsa-lib , which I don't want as I don't use sound;
this is still the case with USE=-alsa.
I want to test what happens if I try to compile it without that dep,
so I copied the ebuild to
On 31/01/13 at 11:38pm, Philip Webb wrote:
I'll give it another try, but suggestions are still welcome.
Thanks for this one.
Maybe you can try adding alsa-lib to package.provided and see if it
builds/works?
--
- Yohan Pereira
The difference between a Miracle and a Fact is exactly the
On Thu, 31 Jan 2013 23:38:27 -0500
Philip Webb purs...@ca.inter.net wrote:
When running `ebuild file digest`, it has to have
all possible files available in order to update the Manifest file.
Those languages won't be installed when you actually install
your modified package. You'll
17 matches
Mail list logo