Re: [gentoo-user] unclear (to me) errors from portage
On 12/08/2014 07:43, J. Roeleveld wrote: Plus, I refuse under any circumstances to run Gentoo on production unless it's backed by a huge build farm or I have a large cluster that are all identical and have very special needs. I use Gentoo exclusively on the servers and desktops at home. I find it easier and more logical to maintain. I do have a VM dedicated to building binary packages though. I just got really tired of eternally being The Only One In The Place Who Knows Gentoo(tm) and who doesn't blindly emerge -uND world on a remote box then walk away At least with apt and yum juniors can be trained fairly quickly to do reliable world updates safely. This keeps the boss off my neck. That makes me happy. On my personal servers and laptops, it will take on the order of atomic warfare to make me give up my beloved Gentoo there :-) -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] akonadi ... don't you just love it?
On 12/08/2014 07:36, J. Roeleveld wrote: On Monday, August 11, 2014 10:45:07 PM Mick wrote: On Monday 11 Aug 2014 20:01:16 Volker Armin Hemmann wrote: isn't it great? back in the days when kmail stored emails in files, everything worked great and even folders with 100k mails were not a problem. But, no, they had to break that. I lost ca 500k emails thanks to akonadi-crap and errors like that. I really loved kmail and thunderbird is garbage compared - but akonadi took away that choice. Thank you, kdepim-devs for making the dumbest decision ever! *thumbsup* I share your feelings although I haven't lost messages in my current attempt to road test kmail2. I am dreading the moment when kmail1 will stop working due to bitrot and I'll have to make a choice. :-( With a modern machine and the latest versions, it's not too bad and responds quicker then kmail-1 did. With the old version, I often had kmail become unresponsive when synchronizing the email. I didn't loose any emails, but that is more likely related to the emails being stored on an imap server, rather then being lucky. I really don't see the point of forcing mysql as a backend. Sqlite would have been a better choice. Way back when in the dark days of KDE-4.4 or thereabouts, the KDE devs did do extensive tests with mysql vs sqlite and found sqlite lacking in horsepower. Remember that it must store the metadata for all your mails and some of us have lots of mail. IIRC there was also serious contention issues with multiple threads. sqlite is an amazing little product, but it does have it's limits. It performs really well as an embedded datastore to replace flat file storage with an SQL interface, and my gut-feel evaluation is that it runs out of steam at similar orders of magnitude of data. Amarok incidentally has almost exactly the same issues and the same solution was adopted -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: akonadi ... don't you just love it?
On Mon, 11 Aug 2014 20:38:57 -0400, Rich Freeman wrote: It appears the recent mysql update broke quite a few things, my MythTV fronted started sulking while the backend just sucked up all the CPU cycles. Something else broke too, but I can't remember more than two things these days. @preserved-rebuild showed nothing but revdep-rebuild cleaned things up. It appears that revdep-rebuild is not ready for retirement yet, although this is the first time in ages that I've needed it. I had a similar experience on two Gentoo boxes, including MythTV. I don't think it was myth itself but rather something in-between. Yes, I think it was dev-qt/qtsql that broke MythTV. I notice that dev-python/mysql-python was rebuilt at the same time, so that must have been missed too, whereas dev-perl/DBD-mysql was re-emerged right after mysql. -- Neil Bothwick Top Oxymorons Number 2: Exact estimate signature.asc Description: PGP signature
Re: [gentoo-user] Re: akonadi ... don't you just love it?
On Mon, Aug 11, 2014 at 08:00:33PM -0500, Dale wrote Neil Bothwick wrote: It appears the recent mysql update broke quite a few things, my MythTV fronted started sulking while the backend just sucked up all the CPU cycles. Something else broke too, but I can't remember more than two things these days. @preserved-rebuild showed nothing but revdep-rebuild cleaned things up. It appears that revdep-rebuild is not ready for retirement yet, although this is the first time in ages that I've needed it. Jeez Neil. If you can remember two things at the same time, you may have me beat. scratches head Now where did that mouse go? Dale They say that memory is the second thing to go. I forget what the first is. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
Re: [gentoo-user] Re: akonadi ... don't you just love it?
On Tuesday 12 August 2014 08:31:34 Neil Bothwick wrote: On Mon, 11 Aug 2014 20:38:57 -0400, Rich Freeman wrote: It appears the recent mysql update broke quite a few things, my MythTV fronted started sulking while the backend just sucked up all the CPU cycles. Something else broke too, but I can't remember more than two things these days. @preserved-rebuild showed nothing but revdep-rebuild cleaned things up. It appears that revdep-rebuild is not ready for retirement yet, although this is the first time in ages that I've needed it. It's so long since I last needed it that I didn't even think of it this time. I had a similar experience on two Gentoo boxes, including MythTV. I don't think it was myth itself but rather something in-between. Yes, I think it was dev-qt/qtsql that broke MythTV. I notice that dev-python/mysql-python was rebuilt at the same time, so that must have been missed too, whereas dev-perl/DBD-mysql was re-emerged right after mysql. It broke kmail here. @preserved-rebuild rebuilt dev-perl/DBD-mysql but didn't catch qtsql. Thank you all for reminding me of revdep-rebuild. -- Regards Peter
Re: [gentoo-user] Re: akonadi ... don't you just love it?
On 12/08/2014 09:57, Walter Dnes wrote: On Mon, Aug 11, 2014 at 08:00:33PM -0500, Dale wrote Neil Bothwick wrote: It appears the recent mysql update broke quite a few things, my MythTV fronted started sulking while the backend just sucked up all the CPU cycles. Something else broke too, but I can't remember more than two things these days. @preserved-rebuild showed nothing but revdep-rebuild cleaned things up. It appears that revdep-rebuild is not ready for retirement yet, although this is the first time in ages that I've needed it. Jeez Neil. If you can remember two things at the same time, you may have me beat. scratches head Now where did that mouse go? Dale They say that memory is the second thing to go. I forget what the first is. mojo? -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] unclear (to me) errors from portage
On Tuesday, August 12, 2014 08:37:52 AM Alan McKinnon wrote: On 12/08/2014 07:43, J. Roeleveld wrote: Plus, I refuse under any circumstances to run Gentoo on production unless it's backed by a huge build farm or I have a large cluster that are all identical and have very special needs. I use Gentoo exclusively on the servers and desktops at home. I find it easier and more logical to maintain. I do have a VM dedicated to building binary packages though. I just got really tired of eternally being The Only One In The Place Who Knows Gentoo(tm) and who doesn't blindly emerge -uND world on a remote box then walk away People who do that should be taken outside behind the chemical shed and shot... At least with apt and yum juniors can be trained fairly quickly to do reliable world updates safely. This keeps the boss off my neck. That makes me happy. I've seen installations start acting really weird because sysadmins decided to update a redhat box the official way (yum). Those usually ended up with backups being restored. It doesn't matter which distribution you use, you still need to test updates on a seperate environment first to ensure all the software running on the environment will still work post-upgrade. On my personal servers and laptops, it will take on the order of atomic warfare to make me give up my beloved Gentoo there :-) Hehe, same here. -- Joost
[gentoo-user] Gentoo mirror list - where?
Hi, if an ebuild file has, e.g., mirror://github/... where do I find the list of mirrors Gentoo is using for that? Many thanks for a hint, Helmut
Re: [gentoo-user] akonadi ... don't you just love it?
On Sunday 10 Aug 2014 10:34:44 J. Roeleveld wrote: On Saturday, August 09, 2014 09:00:48 PM Mick wrote: First some general observations that relate to kmail2: I thought of giving the latest kmail-4.12.5 a spin. So installed it on a machine and set up a couple of IMAP4 servers to get messages from. An account with a messages in the low hundreds works fine. An account with messages in the 100k plus range works like a dog. While kmail fetches headers and then akonadi sets off to organise threads and whatever else it wants to do the application becomes pretty much unresponsive and the CPU climbs up to 98%. Half an hour later I can get back to it. :-@ Anyway, this is not the current problem. I updated mysql to 5.5.39, then I kmail would not start with akonadi failing with mysql log containing errors. So I ran: snipped Why do you run unstable mysql with stable kmail? mysql-5.5.39 is stable now. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] akonadi ... don't you just love it?
On Tuesday 12 Aug 2014 07:42:46 Alan McKinnon wrote: On 12/08/2014 07:36, J. Roeleveld wrote: On Monday, August 11, 2014 10:45:07 PM Mick wrote: On Monday 11 Aug 2014 20:01:16 Volker Armin Hemmann wrote: isn't it great? back in the days when kmail stored emails in files, everything worked great and even folders with 100k mails were not a problem. But, no, they had to break that. I lost ca 500k emails thanks to akonadi-crap and errors like that. I really loved kmail and thunderbird is garbage compared - but akonadi took away that choice. Thank you, kdepim-devs for making the dumbest decision ever! *thumbsup* I share your feelings although I haven't lost messages in my current attempt to road test kmail2. I am dreading the moment when kmail1 will stop working due to bitrot and I'll have to make a choice. :-( With a modern machine and the latest versions, it's not too bad and responds quicker then kmail-1 did. With the old version, I often had kmail become unresponsive when synchronizing the email. I didn't loose any emails, but that is more likely related to the emails being stored on an imap server, rather then being lucky. I really don't see the point of forcing mysql as a backend. Sqlite would have been a better choice. Way back when in the dark days of KDE-4.4 or thereabouts, the KDE devs did do extensive tests with mysql vs sqlite and found sqlite lacking in horsepower. Remember that it must store the metadata for all your mails and some of us have lots of mail. IIRC there was also serious contention issues with multiple threads. sqlite is an amazing little product, but it does have it's limits. It performs really well as an embedded datastore to replace flat file storage with an SQL interface, and my gut-feel evaluation is that it runs out of steam at similar orders of magnitude of data. Amarok incidentally has almost exactly the same issues and the same solution was adopted Only to add that it's more than just mail. It is the meta/data of the whole caboodle of the PIM suite of applications. I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Gentoo mirror list - where?
On Tue, 12 Aug 2014 10:42:34 +0200, Helmut Jarausch wrote: if an ebuild file has, e.g., mirror://github/... where do I find the list of mirrors Gentoo is using for that? From memory (see other thread) emerge -fp cat/pkg. -- Neil Bothwick Deja Moo: The feeling that you heard this bull somewhere before. signature.asc Description: PGP signature
Re: [gentoo-user] Gentoo mirror list - where?
On 08/12/2014 12:21:09 PM, Neil Bothwick wrote: On Tue, 12 Aug 2014 10:42:34 +0200, Helmut Jarausch wrote: if an ebuild file has, e.g., mirror://github/... where do I find the list of mirrors Gentoo is using for that? From memory (see other thread) emerge -fp cat/pkg. Yes, thanks a lot, Helmut
[gentoo-user] Re: Emerge of sys-devel/llvm-3.3-r3 fails....
Volker Armin Hemmann wrote: Am 10.08.2014 um 08:33 schrieb Christopher Kurtis Koeber: *emerge --info =sys-devel/llvm-3.3-r3::gentoo*: Pastebin: http://pastebin.com/qF92DXSY I am not a fan of that. gcc-4.7.3, Intel-R-_Atom-TM *End Section of Build Log*: Pastebin: http://pastebin.com/HEkMicgw or that. /var/tmp/portage/sys-devel/llvm-3.3-r3/work/llvm-3.3.src/tools/llvm- readobj/Error.cpp:49:1: internal compiler error: Segmentation fault Any assistance will be greatly appreciated. did you search bugs.gentoo.org? Lots of llvm stuff there https://bugs.gentoo.org/show_bug.cgi?id=500032#c9 looks like a good fit.
Re: [gentoo-user] Emerge of sys-devel/llvm-3.3-r3 fails....
On Sunday, August 10, 2014 02:33:40 AM Christopher Kurtis Koeber wrote: Hello, I am attempting to emerge xorg-server and sys-devel/llvm-3.3-r3 is pulled in as a dependency. So, when I emerge llvm it fails. Here is some relevant output: emerge --info =sys-devel/llvm-3.3-r3::gentoo: Pastebin: http://pastebin.com/qF92DXSY End Section of Build Log: Pastebin: http://pastebin.com/HEkMicgw Any assistance will be greatly appreciated. Please do not use pastebin or similar services. This list is archived and posted issues with their solutions only make sense as long as all the information remains available. Pastebin and similar services do not have the necessary retention period. Additionally, many people on this list will not even be responding. -- Joost
Re: [gentoo-user] akonadi ... don't you just love it?
On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: Emerge of sys-devel/llvm-3.3-r3 fails....
Am 12.08.2014 um 12:52 schrieb Jouni Kosonen: Volker Armin Hemmann wrote: Am 10.08.2014 um 08:33 schrieb Christopher Kurtis Koeber: *emerge --info =sys-devel/llvm-3.3-r3::gentoo*: Pastebin: http://pastebin.com/qF92DXSY I am not a fan of that. gcc-4.7.3, Intel-R-_Atom-TM *End Section of Build Log*: Pastebin: http://pastebin.com/HEkMicgw or that. /var/tmp/portage/sys-devel/llvm-3.3-r3/work/llvm-3.3.src/tools/llvm- readobj/Error.cpp:49:1: internal compiler error: Segmentation fault Any assistance will be greatly appreciated. did you search bugs.gentoo.org? Lots of llvm stuff there https://bugs.gentoo.org/show_bug.cgi?id=500032#c9 looks like a good fit. could be - I had build failures caused by the -ftracer cflag - which shows nicely the fragility of the whole mess.
Re: [gentoo-user] akonadi ... don't you just love it?
On 12 August 2014 14:06:07 CEST, Alan McKinnon alan.mckin...@gmail.com wrote: On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small Not necessarily. People who care about databases actually supporting SQL properly and performing properly will prefer PostgreSQL. I don't like to be forced to run a MySQL instance as well. It's often the laziness of developers that causes the difficulty of supporting a different database when they started with MySQL. If you start with a different one, like PostgrSQL, supporting different database engines is very simple. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] akonadi ... don't you just love it?
On 12/08/2014 15:28, J. Roeleveld wrote: On 12 August 2014 14:06:07 CEST, Alan McKinnon alan.mckin...@gmail.com wrote: On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small Not necessarily. People who care about databases actually supporting SQL properly and performing properly will prefer PostgreSQL. I don't like to be forced to run a MySQL instance as well. It's often the laziness of developers that causes the difficulty of supporting a different database when they started with MySQL. If you start with a different one, like PostgrSQL, supporting different database engines is very simple. I don't think you read what I said. I didn't say postgresql shouldn't be supported, I said it would always end up being a second class citizen as the number of people who'd be happy with mysql will vastly outnumber the number of people who highly desire postgresql. So, logically, a postgresql driver in this case will probably just bitrot away. Whihc nicely explains the likely reason why that driver is not there. People like yourself who care about databases are very much in the minority of users, even on Linux. Most users across the boards just don't give a shit. Them's the breaks. -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] akonadi ... don't you just love it?
On Tuesday, August 12, 2014 03:38:15 PM Alan McKinnon wrote: On 12/08/2014 15:28, J. Roeleveld wrote: On 12 August 2014 14:06:07 CEST, Alan McKinnon alan.mckin...@gmail.com wrote: On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small Not necessarily. People who care about databases actually supporting SQL properly and performing properly will prefer PostgreSQL. I don't like to be forced to run a MySQL instance as well. It's often the laziness of developers that causes the difficulty of supporting a different database when they started with MySQL. If you start with a different one, like PostgrSQL, supporting different database engines is very simple. I don't think you read what I said. Sorry, didn't read the below in what you put. I didn't say postgresql shouldn't be supported, I said it would always end up being a second class citizen as the number of people who'd be happy with mysql will vastly outnumber the number of people who highly desire postgresql. So, logically, a postgresql driver in this case will probably just bitrot away. Whihc nicely explains the likely reason why that driver is not there. It wouldn't bitrot away as there would be people willing to keep it working, provided it wouldn't require a MySQL - SQL translator to be kept up-to-date. People like yourself who care about databases are very much in the minority of users, even on Linux. Most users across the boards just don't give a shit. Them's the breaks. Users never care about what they install. I just wish the majority of developers would actually be willing to follow some simple guidelines to make it actually possible to others to write and maintain the drivers to connect to different databases. Several attempts have been made by people to add support for different databases to various projects. I've tried to do it myself on occasion, but even when patches are accepted by upstream, they get broken by upstream at a future release again because of the bad design that is often employed by lazy developers. -- Joost
Re: [gentoo-user] Re: akonadi ... don't you just love it?
On 08/12/2014 12:31 AM, Neil Bothwick wrote: Yes, I think it was dev-qt/qtsql that broke MythTV. I notice that dev-python/mysql-python was rebuilt at the same time, so that must have been missed too, whereas dev-perl/DBD-mysql was re-emerged right after mysql. It most definitely was, I just updated my backend and 3 remote frontends and had this issue. Portage missed this completely, it was revdep-rebuild that found this breakage and repaired it. From what I remember there was a python sql package that wound up being broken too. Dan
Re: [gentoo-user] Re: akonadi ... don't you just love it?
On Tue, Aug 12, 2014 at 10:38 AM, Daniel Frey djqf...@gmail.com wrote: On 08/12/2014 12:31 AM, Neil Bothwick wrote: Yes, I think it was dev-qt/qtsql that broke MythTV. I notice that dev-python/mysql-python was rebuilt at the same time, so that must have been missed too, whereas dev-perl/DBD-mysql was re-emerged right after mysql. It most definitely was, I just updated my backend and 3 remote frontends and had this issue. Portage missed this completely, it was revdep-rebuild that found this breakage and repaired it. From what I remember there was a python sql package that wound up being broken too. Yup. My frontends broke after updating the backend. Clearly there is some kind of incompatibility between client/server cross-version. This isn't just a linking issue. I suspect qtsql was the issue - I just didn't recall that when I made my last post. Rich
[gentoo-user] Portage metadata cache backend: sqlite or not?
Hi list For the longest time I've had portage configured to use the sqlite metadata cache backend as per an old HOWTO [0], however, I thought that it would be a good idea to revisit that decision. Now apparently, this was supposed to speed up portage, although even that depends. For instance, [0] says that the metadata_overlay backend is faster on fast storage; since all of portage is on an SSD, that ought to be the case for me. However, [0] is pretty outdated, so I don't really know, and don't have any comparison. In addition to that, I don't explicitly make use of the sqlite metadata cache, that is, I don't (consciously) use any software that accesses those DBs, except for eix (except for overlays, where one would need to run emerge --regen first, which is *sllw*), which can make use of them if CACHE_METHOD is set appropriately; this speeds up eix-update considerably. Does anybody here have experience with this, or a recommendation? I tried switching to the default cache method temporarily to see how things perform, and emerge @world -uDNva slowed down by about 30 seconds, so preliminary results point to sticking with sqlite (although it could at least partly be a btrfs performance regression in Linux 3.15, since there have been several reports of those, and several fixes slated for 3.16). Anyway, I'm also unsure of unintended consequences, or other settings I might have to change, too. Also, does anybody have any performance data and/or experience on using btrfs with compression in this context? [0] http://www.gentoo-wiki.info/TIP_speed_up_portage_with_sqlite Greetings, -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup signature.asc Description: PGP signature
Re: [gentoo-user] akonadi ... don't you just love it?
Am 12.08.2014 um 16:10 schrieb J. Roeleveld: On Tuesday, August 12, 2014 03:38:15 PM Alan McKinnon wrote: On 12/08/2014 15:28, J. Roeleveld wrote: On 12 August 2014 14:06:07 CEST, Alan McKinnon alan.mckin...@gmail.com wrote: On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small Not necessarily. People who care about databases actually supporting SQL properly and performing properly will prefer PostgreSQL. I don't like to be forced to run a MySQL instance as well. It's often the laziness of developers that causes the difficulty of supporting a different database when they started with MySQL. If you start with a different one, like PostgrSQL, supporting different database engines is very simple. I don't think you read what I said. Sorry, didn't read the below in what you put. I didn't say postgresql shouldn't be supported, I said it would always end up being a second class citizen as the number of people who'd be happy with mysql will vastly outnumber the number of people who highly desire postgresql. So, logically, a postgresql driver in this case will probably just bitrot away. Whihc nicely explains the likely reason why that driver is not there. It wouldn't bitrot away as there would be people willing to keep it working, provided it wouldn't require a MySQL - SQL translator to be kept up-to-date. People like yourself who care about databases are very much in the minority of users, even on Linux. Most users across the boards just don't give a shit. Them's the breaks. Users never care about what they install. I just wish the majority of developers would actually be willing to follow some simple guidelines to make it actually possible to others to write and maintain the drivers to connect to different databases. Several attempts have been made by people to add support for different databases to various projects. I've tried to do it myself on occasion, but even when patches are accepted by upstream, they get broken by upstream at a future release again because of the bad design that is often employed by lazy developers. -- Joost wasn't qtsql once supposed to that?
Re: [gentoo-user] akonadi ... don't you just love it?
On 12 August 2014 20:21:03 CEST, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am 12.08.2014 um 16:10 schrieb J. Roeleveld: On Tuesday, August 12, 2014 03:38:15 PM Alan McKinnon wrote: On 12/08/2014 15:28, J. Roeleveld wrote: On 12 August 2014 14:06:07 CEST, Alan McKinnon alan.mckin...@gmail.com wrote: On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small Not necessarily. People who care about databases actually supporting SQL properly and performing properly will prefer PostgreSQL. I don't like to be forced to run a MySQL instance as well. It's often the laziness of developers that causes the difficulty of supporting a different database when they started with MySQL. If you start with a different one, like PostgrSQL, supporting different database engines is very simple. I don't think you read what I said. Sorry, didn't read the below in what you put. I didn't say postgresql shouldn't be supported, I said it would always end up being a second class citizen as the number of people who'd be happy with mysql will vastly outnumber the number of people who highly desire postgresql. So, logically, a postgresql driver in this case will probably just bitrot away. Whihc nicely explains the likely reason why that driver is not there. It wouldn't bitrot away as there would be people willing to keep it working, provided it wouldn't require a MySQL - SQL translator to be kept up-to-date. People like yourself who care about databases are very much in the minority of users, even on Linux. Most users across the boards just don't give a shit. Them's the breaks. Users never care about what they install. I just wish the majority of developers would actually be willing to follow some simple guidelines to make it actually possible to others to write and maintain the drivers to connect to different databases. Several attempts have been made by people to add support for different databases to various projects. I've tried to do it myself on occasion, but even when patches are accepted by upstream, they get broken by upstream at a future release again because of the bad design that is often employed by lazy developers. -- Joost wasn't qtsql once supposed to that? If a framework like qtsql is used, swapping the database is easy. Most developers seem to prefer to reinvent the wheel and often come up with something that vaguely resembles a circle and is held together with a mixture of glue and duck tape. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] akonadi ... don't you just love it?
On 12/08/2014 21:00, J. Roeleveld wrote: On 12 August 2014 20:21:03 CEST, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am 12.08.2014 um 16:10 schrieb J. Roeleveld: On Tuesday, August 12, 2014 03:38:15 PM Alan McKinnon wrote: On 12/08/2014 15:28, J. Roeleveld wrote: On 12 August 2014 14:06:07 CEST, Alan McKinnon alan.mckin...@gmail.com wrote: On 12/08/2014 11:10, Mick wrote: I recall the devs explicitly stating early enough in the KDE4 development that sqlite is not man enough for the job and advising everyone to move over to mysql. Someone was looking at postgresql as an alternative to mysql, but I'm not sure that this would bring any benefit. pg is a fine database, but for this use will always be a 2nd class citizen. Most users will already have mysql installed, or will be willing to install it. The number of folks with pg and without mysql will probably be small Not necessarily. People who care about databases actually supporting SQL properly and performing properly will prefer PostgreSQL. I don't like to be forced to run a MySQL instance as well. It's often the laziness of developers that causes the difficulty of supporting a different database when they started with MySQL. If you start with a different one, like PostgrSQL, supporting different database engines is very simple. I don't think you read what I said. Sorry, didn't read the below in what you put. I didn't say postgresql shouldn't be supported, I said it would always end up being a second class citizen as the number of people who'd be happy with mysql will vastly outnumber the number of people who highly desire postgresql. So, logically, a postgresql driver in this case will probably just bitrot away. Whihc nicely explains the likely reason why that driver is not there. It wouldn't bitrot away as there would be people willing to keep it working, provided it wouldn't require a MySQL - SQL translator to be kept up-to-date. People like yourself who care about databases are very much in the minority of users, even on Linux. Most users across the boards just don't give a shit. Them's the breaks. Users never care about what they install. I just wish the majority of developers would actually be willing to follow some simple guidelines to make it actually possible to others to write and maintain the drivers to connect to different databases. Several attempts have been made by people to add support for different databases to various projects. I've tried to do it myself on occasion, but even when patches are accepted by upstream, they get broken by upstream at a future release again because of the bad design that is often employed by lazy developers. -- Joost wasn't qtsql once supposed to that? If a framework like qtsql is used, swapping the database is easy. Most developers seem to prefer to reinvent the wheel and often come up with something that vaguely resembles a circle and is held together with a mixture of glue and duck tape. I blame php and others of it's ilk. The good thing about php is that everyone and their dog can knock out running code. The bad thing about php is that they do. Substitute mysql and bash if you will and tweak the content to suit - it all works out the same. Sensible languages (like, oh I dunno - python maybe?) have this trick about them - you have to work hard to write awful code. You also have to work hard to write awesome code, but if you just follow the book you usually end up with acceptable code. I will refrain from commenting on perl. -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] Re: Portage metadata cache backend: sqlite or not?
Marc Joliet marcec at gmx.de writes: Hi list For the longest time I've had portage configured to use the sqlite metadata cache backend as per an old HOWTO [0], however, I thought that it would be a good idea to revisit that decision. Does anybody here have experience with this, or a recommendation? I cannot directly speak to your issues. But, a while back when I was researching some dB tools, I discovered a add-on for browsers that allows you to view sqllite db: SQLite Manager 0.8.1 and this interesting tool: http://sqlitestudio.pl/ I hope this helps you diagnose your problems. James
Re: [gentoo-user] XFCE4: How cab I disable Restart and Shut down buttons?
On Mon, Aug 11, 2014 at 5:05 AM, Johannes Geiss johannes.ge...@web.de wrote:
Hello there,
I have XFCE4 and Systemd running and I want to know if it is possible
to disable or remove the buttons Restart and Shut down at the
logout dialog (xfce4-session-logout).
If so, how?
(Sorry I took so long, I was updating my system).
You want to disable only the buttons, or the functionality? For one
user, or several?
Assuming you want to disable the functionality for one user, this
disables both the functionality *AND* the buttons (they show up grayed
out):
$ cat /etc/polkit-1/rules.d/10-no-restart-shutdown.rules
polkit.addRule(function(action, subject) {
if (subject.user == myuser) {
if (action.id.match(org.freedesktop.login1.power-off) ||
action.id.match(org.freedesktop.login1.reboot)) {
return polkit.Result.NO;
}
}
});
Of course, change myuser for the user you want to disable this. You
can also use groups (subject.isInGroup(group)), or use suspend or
hibernate instead of reboot.
This works for any desktop that uses systemd (logind, technically) for
session tracking: AFAIK, this should work for at least GNOME, Xfce,
and KDE.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
Re: [gentoo-user] Portage metadata cache backend: sqlite or not?
On Tue, Aug 12, 2014 at 11:40 PM, Marc Joliet mar...@gmx.de wrote: Hi list For the longest time I've had portage configured to use the sqlite metadata cache backend as per an old HOWTO [0], however, I thought that it would be a good idea to revisit that decision. Now apparently, this was supposed to speed up portage, although even that depends. For instance, [0] says that the metadata_overlay backend is faster on fast storage; since all of portage is on an SSD, that ought to be the case for me. However, [0] is pretty outdated, so I don't really know, and don't have any comparison. In addition to that, I don't explicitly make use of the sqlite metadata cache, that is, I don't (consciously) use any software that accesses those DBs, except for eix (except for overlays, where one would need to run emerge --regen first, which is *sllw*), which can make use of them if CACHE_METHOD is set appropriately; this speeds up eix-update considerably. Does anybody here have experience with this, or a recommendation? I tried switching to the default cache method temporarily to see how things perform, and emerge @world -uDNva slowed down by about 30 seconds, so preliminary results point to sticking with sqlite (although it could at least partly be a btrfs performance regression in Linux 3.15, since there have been several reports of those, and several fixes slated for 3.16). Anyway, I'm also unsure of unintended consequences, or other settings I might have to change, too. Also, does anybody have any performance data and/or experience on using btrfs with compression in this context? [0] http://www.gentoo-wiki.info/TIP_speed_up_portage_with_sqlite Greetings, -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup Having tried this feature, I'd advise against it. It takes long time to generate metadata after sync and not really that advantageous. Also eix has it's own issues in this mode.
