Alan McKinnon wrote:
> You know what? I'm not convinced.
>
> What I'm seeing is a rather large towering edifice of complexity to deal
> with a problem that is not the general case.
I find it funny that perhaps you did not realize that you repeated
the main argument *in favour of subslots* on the
On Tuesday 05 Nov 2013 10:52:36 Martin Vaeth wrote:
> Note, however, "in the long run": The process of transforming all
> packages to subslot dependencies is not yet complete.
> I guess it will take many years until it is: Up to some corner cases
> you can check whether the process is complete for
On 05/11/2013 11:52, Martin Vaeth wrote:
> Alan McKinnon wrote:
>> You know what? I'm not convinced.
>>
>> What I'm seeing is a rather large towering edifice of complexity to deal
>> with a problem that is not the general case.
>
> I find it funny that perhaps you did not realize that you repeate
Am Tue, 05 Nov 2013 12:14:59 +0200
schrieb Alan McKinnon :
> On 05/11/2013 11:52, Martin Vaeth wrote:
> > Alan McKinnon wrote:
> >> You know what? I'm not convinced.
> >>
> >> What I'm seeing is a rather large towering edifice of complexity to deal
> >> with a problem that is not the general case
On Sat, Nov 02, 2013 at 01:04:52PM +0100, hasufell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Another round of questioning the users here.
>
> more specifically:
> * how often do you experience useless rebuilds?
> * do you really have a problem with running
> revdep-rebuild/hask
Alan McKinnon writes:
Excuse the top-posting; if I try inter-post between all those blockers
you'll never find what I reply :-)
I would, but for everyone else it's a mess. E-mail with line breaks is
not suited for this kind of output.
First I recommend to sync your tree again, just in case y
On Tue, Nov 05, 2013 at 07:29:28AM -0600, Bruce Hill wrote:
> On Sat, Nov 02, 2013 at 01:04:52PM +0100, hasufell wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Another round of questioning the users here.
> >
> > more specifically:
> > * how often do you experience useless r
On Tue, Nov 05, 2013 at 06:15:56AM +, Nuno J. Silva (aka njsg) wrote:
> >> On Monday 04 Nov 2013 19:51:32 Alexander Kapshuk wrote:
> >> > On 11/03/2013 02:27 AM, Daniel Campbell wrote:
> >> > > For starters, you should probably merge package.keywords into
> >> > > package.accept_keywords; the l
On 05/11/2013 14:11, Marc Joliet wrote:
> Am Tue, 05 Nov 2013 12:14:59 +0200
> schrieb Alan McKinnon :
>
>> On 05/11/2013 11:52, Martin Vaeth wrote:
>>> Alan McKinnon wrote:
You know what? I'm not convinced.
What I'm seeing is a rather large towering edifice of complexity to deal
>
On 05/11/2013 15:37, Alex Schuster wrote:
>> Portage and the tree by itself isn't doing it, here's my output:
>>
>> $ emerge -pvt fsrunner
>>
>> These are the packages that would be merged, in reverse order:
>>
>> Calculating dependencies... done!
>> [ebuild N ] kde-misc/fsrunner-0.7.5:4 USE=
On Tue, Nov 05, 2013 at 04:44:43PM +0200, Alan McKinnon wrote:
>
> I too see your viewpoint, as you see mine. There's nothing wrong with
> your logic within the narrow domain of making the code that implements
> this specific feature (subslots) work correctly per spec.
>
> Background: I'm a Linux
Alan McKinnon wrote:
>
> It seems to me that you didn't read the whole post fully, and have
> cherry-picked a part that you think bolsters your position.
I do not think that I have a position here.
Subslots solve some problem. If they cause inconveniences
like portage needing too long or frequen
On 05/11/2013 17:21, Bruce Hill wrote:
> That is good practice, to say the least. Wish it would happen in Gentoo. But
> then again, may I ask, do you have as many devs and as many pkgs that must
> co-exist on so many differently configured machines?
Not even close :-)
What we lack in package dive
On 05/11/2013 20:06, Martin Vaeth wrote:
>> I predict once a week fallout from sub-slots induced bugs that was
>> > intended to fix once a year problem.
> Let's see: Forgetting to bump a subslot means that the purpose of
> subslots for that package fails. A problem, but not worse than
> without sub
I was referred back to my distro supplier for a kernel crash. Isn't
that a kernel problem?
https://bugzilla.kernel.org/show_bug.cgi?id=62981
- Grant
On Tuesday 05 Nov 2013 06:15:56 Nuno J. Silva (aka njsg) wrote:
> On 2013-11-05, Bruce Hill wrote:
> > On Mon, Nov 04, 2013 at 10:43:07PM +, Mick wrote:
> >> On Monday 04 Nov 2013 19:51:32 Alexander Kapshuk wrote:
> >> > On 11/03/2013 02:27 AM, Daniel Campbell wrote:
> >> > > For starters, you
On Tue, 5 Nov 2013 08:29:59 -0600, Bruce Hill wrote:
> I can't understand the *need* for the new slot/subslot philosophy.
The need to it is clear. Previous methods worked by breaking things and
then fixing them, hopefully before the breakage became a problem,
whenever library APIs changed. Subslo
On Tue, Nov 05, 2013 at 09:28:05PM +, Neil Bothwick wrote:
> On Tue, 5 Nov 2013 08:29:59 -0600, Bruce Hill wrote:
>
> > I can't understand the *need* for the new slot/subslot philosophy.
>
> The need to it is clear. Previous methods worked by breaking things and
> then fixing them, hopefully
On Tue, Nov 05, 2013 at 12:02:00PM -0800, Grant wrote:
> I was referred back to my distro supplier for a kernel crash. Isn't
> that a kernel problem?
>
> https://bugzilla.kernel.org/show_bug.cgi?id=62981
The first thing for any crash is logs. And btw ... don't go to the Linux
kernel if you're ru
Re , Nikos Chantziaras said:
> Since quite a while ago (months), acroread stopped working.
Side note, evince works for me on ~amd64 for viewing pdf. It also seems
to work ok with fillable pdf.
https://projects.gnome.org/evince/
-- Keith
-- ~~
Hello,
poppler fails to build for me and i don't know why.
Does someone got an idea about this?
[ 97%] Building CXX object
qt4/src/CMakeFiles/poppler-qt4.dir/ArthurOutputDev.cc.o
cd
/var/tmp/portage/app-text/poppler-0.24.3/work/poppler-0.24.3_build/qt4/src
&& /usr/bin/x86_64-pc-linux-gnu-g++ -DH
Alan McKinnon wrote:
>
> You don't have to keep explaining subslots to me
But not every reader knows the details - this is not a private
conversation.
> What I have maintained all along is that I don't see the solution as
> tested to be production-ready
It has been in ~arch for many months, and
22 matches
Mail list logo
