Re: [gentoo-dev] [RFC] Restricted version of gentoo-dev mailing list

On 27/05/17 18:17, Patrick Lauer wrote: > But you do gentoo wrong, so as a user I'd like you to reconsider what > you wrote there and maybe take a long vacation. I too do not hate our users (in which I include myself). Treating users as a worthless nuisance, unless they're writing ebuilds or mana

Re: [gentoo-dev] Changing PMS to Portage Manager Specification

While the PMS perhaps hasn't been an unequivocal success, it's still a good effort with some success. I would be disappointed to see the proposed change, and view it as a bad sign for Gentoo. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPG

Re: [gentoo-dev] Last-rites: app-arch/unrar-gpl

Just a note in case anyone is relying on this package for RAR files; check out unar. It's LGPL, and works for e.g. RARv3. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-dev] Last-rites: app-arch/unrar-gpl

On 31/08/17 09:37, Vladimir Romanov wrote: > But does it work for RAR5? Give me a RAR5, and I can test it for you. -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: [gentoo-dev] Last-rites: app-arch/unrar-gpl

On 31/08/17 09:49, Vladimir Romanov wrote: > I've attached "old" rar_v3.rar and "new" rar_v4.rar. Works fine. :) -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander signature.asc Description: OpenPGP digital signature

Re: That's all folks. (Re: OT Re: [gentoo-dev] Re: [gentoo-project] [RFC] Splitting developer-oriented and expert user mailing lists)

On 08/12/17 21:22, Andreas K. Huettel wrote: > > Independent of whether William now unsubscribed or not, he's now enjoying a > lengthy (1 year until review) vacation from all Gentoo communication channels. > This seems like a meaningless thing to post at this point. And you might want to conside

Re: [gentoo-dev] Re: repo/gentoo:master commit in: dev-libs/libunibreak/

On 14/12/17 17:09, David Seifert wrote: >> So I can add tons of broken packages, sprinkled over different >> days, hidden between other valid bumps, and can then tell people >> they need to lastrite this stuff first and do the 30-day rain >> dance? Come on, even for Gentoo standards, that's absolut

Re: [gentoo-dev] [QA] New policy: 'files' directory must not be larger than 32 KiB

On 17/12/17 20:35, Lars Wendler wrote: >> On Sun, Dec 17, 2017 at 1:39 PM, Mike Gilbert >> wrote: >>> I just want to voice my opinion on this: as a developer, this >>> policy is a royal pain in the ass. >>> >>> I would ask the council to please increase this limit to at >>> least 100 KiB, prefer

Re: [gentoo-dev] Upcoming posting restrictions on the gentoo-dev mailing list

On 10/01/18 08:55, Lars Wendler wrote: > Seems we're turning into an elitist club or something... Gentoo has already had the reputation of being an elitist club for years. As such I'd like to see steps to remedy this status, rather than taking steps like this, which just exacerbates the unfortunat

Re: [gentoo-dev] Mailing list moderation and community openness

On 20/03/18 13:17, Michael Palimaka wrote: > Could someone please explain how this doesn't directly contradict the > core tenets of an open and inclusive community? It's fairly simple to produce a justification of the decision. I can think of several ways of doing so. One is through an appeal to so

Re: [gentoo-dev] Mailing list moderation and community openness

On 22/03/18 07:31, Benda Xu wrote: > We might be able to require GPG signed email to make a post. Almost definitely. But before bikeshedding that, it would be advisable to find out whether it would be a good idea in the first place. Unless you want only prospective developers to be able to contrib

Re: [gentoo-dev] Re: games.eclass policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FWIW, I tried contacting the games team members via IRC and email a few times over a few years, but never got even a simple "hello" out of them. So I gave up. And I've heard several similar tales confirmed by established developers. So maybe they're

[gentoo-dev] Re: [PATCH] change how the tmp file for the commit msg is made

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 There's only superficial changes required to the commit message required -- capitalise the message, s/This changes/change/ in the description -- it looks good otherwise. However, I don't know whether this patch is *desired*. Doug, do you have a bug

Re: [gentoo-dev] [RFC] Global USE=gui

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/06/16 11:27, James Le Cuirot wrote: > I don't think that's unreasonable given that it only does that > when qt4 and gtk3 are disabled. It is horribly counter-intuitive. -qt5 should never result in qt5. > Some packages require qt5 unconditional

Re: [gentoo-dev] [RFC] Global USE=gui

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/06/16 13:27, James Le Cuirot wrote: > What does that mean? It means that it is made explicit in some way clearly visible to the end-user. > Take www-client/otter, for example. It's a qt5-based browser. It > doesn't have the qt5 flag. How can

Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Friends, It would be wise of us to create a novel way of involving users from the ashes of Sunrise. Here is my suggestion: It would be fruitful to encourage every single Gentoo user to have their own repository. And this repository should be public

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/06/16 16:39, Zac Medico wrote: > The first obstacle that comes to my mind is how to discover the > packages. There needs to be a central index of repositories which > includes searchable metadata for all of the packages provided by > those re

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/06/16 16:53, Consus wrote: > How all those people are expected to coordinate their work? I don't want to control this. That's up to them. It works well in Exherbo and NixOS. But I agree that tooling to support it would be useful. - -- Alexand

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/06/16 16:53, Rich Freeman wrote: > Do you propose that you can have cross-repo dependencies? Sure. This works well in Exherbo using Paludis. We could do it right now if we wanted to. > If so that creates a lot of potential issues, even if you

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/06/16 17:53, james wrote: >> DEAL? No thanks. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJXWTpTAAoJENQqWdRUGk8BPAsQAM1vjeh7AzBx8yVGHcZ0U+vJ RNoIDrF05PL

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 08/06/16 18:15, Peter Stuge wrote: > Do NOT - I repeat NOT - tie "user repos" to GitHub Inc. If I were in charge or to be involved, I would not even dream about tying users to a proprietary SaaS. That would be highly unethical in my view. - -- A

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 01:08, Andreas K. Huettel wrote: > Sigh. Every 2 years somebody else comes up with the same silly > idea. I stopped reading your email after this sentence. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGI

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 11:45, M. J. Everitt wrote: > Btw, your key is showing up as expired, Alex. It doesn't expire until next year. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIc

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 11:55, Daniel Campbell wrote: > According to Enigmail, it expired April 19th. I suggest you refresh your keys. My signing subkey was signed April 20th and expires in 2017. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~al

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 12:14, Johannes Huber wrote: > This statement is not feeded with numbers. Distrowatch tells > something else. I don't know what "feeded" means. Distrowatch is useless for anything but figuring out what distros are popular among people wh

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 12:20, Rich Freeman wrote: > Perhaps you could explain how they actually prevent the issues I > brought up? You should probably ask the Exherbo developers, not me. > > Suppose you have 10 packages, and they each depend on zlib from a >

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 12:28, Igor Savlook wrote: > Ok how coordinate? Example: I install packageA in exherbo from > repository1 and packageA denend on packageB on repository2. Now > packageB removed from repository2 and exherbo crash on install > package or

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/06/16 22:15, Michał Górny wrote: > Didn't you just contradict yourself? First you tell that everyone > should have their own public repo... then you tell that we should > merge stuff from those repos. So are you targeting split-repo > model,

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/06/16 09:39, M. J. Everitt wrote: > So forgive me for being blind .. but we were talking about going > -away- from central, curated repositories, and now we've come full > circle to the situation we have now with overlays, mostly > controlled

Re: [gentoo-dev] Packages up for grabs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/06/16 22:37, Pacho Ramos wrote: > sys-apps/razercfg I'm not an ebuild person, but if someone could maintain this I would be grateful. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/06/16 11:33, Consus wrote: > That's great, but how are you gonna prevent nodejs-like > clusterfuck[?] By not being nodejs. The core repos are curated and reviewed. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BE

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/06/16 12:38, Rich Freeman wrote: > So, I was chatting with an Exherbo dev. Their model isn't quite > what your earlier emails seemed to suggest (at least as I read > it). You should get them to reply to this thread, because... > As I underst

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/06/16 17:32, Ian Stakenvicius wrote: > On 10/06/16 03:53 AM, Alexander Berntsen wrote: >> ... Their repositories would likely be amalgamations of our >> curated and reviewed repositories ... > Could you elaborate on wha

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/06/16 18:18, Rich Freeman wrote: > And my understanding again for Exherbo And it is wrong again, according to an Exherbo user I talked to. Please get your Exherbo developer to participate directly, because I think you are having some trouble co

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/06/16 09:00, Michał Górny wrote: > If you are not going to maintain your contribution, we can't > guarantee it will be accepted. I'm certainly not interested in > having to worry about 20 more maintainer-needed packages next month > because som

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 13/06/16 09:54, M. J. Everitt wrote: > I really think someone needs to do a bit of portageq and see what > the Tree *actually* contains > > Likewise .. a trek through bugzilla would also be enlightening for > those not familiar ... > > On

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 13/06/16 10:09, M. J. Everitt wrote: > Excuse me .. and this thread emerged from deprecating the EXACT > thing you are suggesting!? I don't know what you are talking about. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 In addition to what Peter Stuge (correctly) identifies as needing to change, there also needs to be a modularisation of Gentoo-curated package repositories. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNA

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 14/06/16 08:48, Daniel Campbell wrote: > What sort of modularization are you talking about? The cheap answer is "as much as possible. > Would we suggest something like GNOME, KDE, XFCE, Mate, Cinnamon, > et al getting their own overlays? dev-lang

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 You've got most things right, Rich. But a couple of comments follow. On 15/06/16 02:25, Rich Freeman wrote: > 1. Developers wouldn't have access to all the ebuilds in the > curated repositories. They would only have access to the ones they > con

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/06/16 09:24, Daniel Campbell wrote: > To touch on the user repo part.. can't it be as simple as adding > one requirement to user repos that wish to be considered as > curated? > > Create a "gentoo-ci" branch or something else, and the maintain

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/06/16 09:34, Daniel Campbell wrote: > There is overhead in choosing which repositories you want to > include in your 'upstream'. Even with an automated tool like > layman, there's maintenance overhead. We'd need another tool to > assist in disc

Re: Facilitating user contributed ebuilds (Was: [gentoo-dev] The future of the Sunrise project)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 16/06/16 09:39, Daniel Campbell wrote: > I guess what I mean is these outside developers could continue > hacking and/or breaking things, or whatever else, without worrying > about their "official" branch. We could have a standard that > assumes

Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 What we have been doing in Portage so far is that when we fix it in git, we put IN_PROGRESS + InVCS, and write a comment that links to the commit on gitweb. Then when we actually release Portage, we consider it to be fixed, and make it RESOLVED. I w

Re: [gentoo-dev] [RFC] bugs.g.o: Merging UNCONFIRMED & CONFIRMED into NEW

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I would like to keep CONFIRMED as I use it and find it useful. I also think that renaming UNCONFIRMED to OPEN is silly and misleading, since any non-RESOLVED bug is indeed an open bug. I don't have anything against renaming it to NEW, although I thi

Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 17/06/16 09:50, Michał Górny wrote: > However, isn't the URL field sufficient for this? This is useful in many cases for describing the bug and similar things when the bug is being reported. Is it possible to have multiple URLs sensibly in this fi

Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I *seriously* object to a RFC that affects so many people lasting *less than 24h*. - -- Alexander berna...@gentoo.org https://secure.plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJXY77iAAoJENQqWdRUGk8BCKIP/3ZG

Re: [gentoo-dev] [RFC] bugs.g.o: Killing VERIFIED state, possibly introducing STABILIZED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 17/06/16 15:58, Rich Freeman wrote: > That could actually be generalized. I could see many types of > bugs where the issue is with upstream, and we might want to track > the progress as upstream implements a fix, releases it, and then it > is sta

[gentoo-dev] Bad GPG key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Why is your signature suddenly bad? It verifies in your 19:06 (GMT+1) submission to gentoo-dev, but not in the most recent one -- 20:24 (GMT+1). - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version:

Re: [gentoo-dev] Bad GPG key

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 28/12/12 20:29, Alexander Berntsen wrote: > Why is your signature suddenly bad? It verifies in your 19:06 > (GMT+1) submission to gentoo-dev, but not in the most recent one -- > 20:24 (GMT+1). > > Sorry. this was for Andreas, a

Re: [gentoo-dev] About using a CONFIGURATION (or SETUP) file under /usr/share/doc for configuration information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/12 00:09, Pacho Ramos wrote: > More examples I saw today when updating: - nvidia-drivers -> things > like telling people to add them to video group could be treated in > the same way, the same probably for eselect instructions. Every game re

[gentoo-dev] Local bindist descriptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All packages should have local descriptions of what the bindist USE-flag specifically does. This should be a policy when writing ebuilds that include it. The bindist USE-flag is for avoiding components in a package that would result in non-re-distri

Re: [gentoo-dev] Local bindist descriptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/12 12:39, Diego Elio Pettenò wrote: > On 30/12/2012 04:03, Mike Gilbert wrote: >> That would be much more effective than a policy that may be >> (accidentally) ignored. > > +1 +1 from me as well. A much simpler and reliable way of achievin

Re: [gentoo-dev] Re: Local bindist descriptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/12 13:15, Nuno J. Silva wrote: > I see his point that emerge will sort of imply what does bindist > do, but it requires running emerge several times with different USE > flag combinations, while just writing a small explanation wouldn't > hu

Re: [gentoo-dev] Re: Local bindist descriptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/12 15:01, Alexis Ballier wrote: > Maybe you could suggest a nice beforehand UI for REQUIRED_USE > constraints. I think this is orthogonal to the discussion. If ffmpeg had a local description of bindist, # equery u ffmpeg would outpu

Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in virtual/ffmpeg: ffmpeg-9.ebuild ChangeLog ffmpeg-0.10.2-r1.ebuild

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 17/01/13 12:02, Ben de Groot wrote: > I have used libav and mplayer2 for a long time, and have not run > into any problems. The only thing missing is mencoder. +1 - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP S

Re: [gentoo-dev] RFC: new "qt" category

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - -1 here. It's a too specific category name. I can appreciate it easing the headaches for the maintainers, but from a design POV I dislike it. (For the record I also dislike KDE/GNOME/XFCE-categories.) - -- Alexander alexan...@plaimi.net http://p

Re: [gentoo-dev] Re: RFC: new "qt" category

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 17/01/13 15:25, Michael Palimaka wrote: > Where would you place the 300ish KDE core packages then? In whatever generic category they belong. I understand that the monolithic nature makes it difficult from a maintainer POV, but from a design POV it

Re: [gentoo-dev] Re: How a proper server profile should look like

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 While I tend towards the cleaner design, not the "don't fix what isn't *broken*" approach -- I'm fine either way. But I think the handbook or some tool should obnoxiously spit the flags (and a minor "justification" for each flag and/or the set of fla

Re: [gentoo-dev] Re: How a proper server profile should look like

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 22/01/13 13:12, Rich Freeman wrote: As a long-time user, I can't put myself in a first-time user's frame of reference. But it would be useful for me whenever I'm installing Gentoo on a new device, if I were able to have the profile's USE-flags li

Re: [gentoo-dev] Lastrites: media-gfx/picasa, dev-python/papyon, net-voip/telepathy-butterfly, sci-visualization/paraview, x11-misc/xdaf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/02/13 12:47, Patrick Lauer wrote: > So instead of moving things from random overlays to the tree we > remove packages now, remove features from other packages because of > that (openfoam) and then ... tell users to use an overlay? > > Someho

Re: [gentoo-dev] Half of the firmware packages in tree install to wrong directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/02/13 05:27, Peter Stuge wrote: > I, as another user, prefer not to have a whole bunch of firmware > installed if I only want one or two of them. +1. Also licences. It's a mess. Not suggesting that *I* have the magic-unicorn-land-perfect solut

Re: [gentoo-dev] Re: [gentoo-dev-announce] RFC: Graveyard project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/02/13 01:19, Diego Elio Pettenò wrote: > The problem is when you have to triple-check that the user hasn't > enabled some random fucked up overlay and you have to guess whether > that might be the cause of the problem. Yes. It's difficult to g

Re: [gentoo-dev] Re: [gentoo-dev-announce] RFC: Graveyard project

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/02/13 13:58, Diego Elio Pettenò wrote: > Freedom is overrated, especially by those who use such sound > bites. Whilst you do get to decide how and if you choose to value my freedom, you most certainly do *not* get to decide how I should rate it

Re: [gentoo-dev] Evaluating a new malloc()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/02/13 14:33, Richard Yao wrote: > The Blender project found some fairly remarkable discrepancies > between what their software actually used and what glibc's ptmalloc > allocated Have they filed a bug? - -- Alexander alexan...@plaimi.net http:

Re: [gentoo-dev] Gentoo Bugday

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27/02/13 01:39, Pavlos Ratis wrote: > I would like to announce you a new try to 'revive' the Bugday > event. I don't have anything to add. I just wanted to express my support. I'm told that it is useful to be supportive of people and that they lik

Re: [gentoo-dev] maintainer-wanted: x11-drivers/nvidia-drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/03/13 08:01, Walter Dnes wrote: > If user-space drivers are really that slow, we may as well stick > with VESA as a fallback. You misunderstood something. «Please realize that this article describes the _in kernel_ interfaces, not the

Re: [gentoo-dev] Make inotify a global USE flag?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21/03/13 11:29, Ulrich Mueller wrote: > Should we make it a global flag? Sure. > What description is better: > > inotify - Enable inotify filesystem monitoring support inotify - > Enable inotify file change notification support > > BTW, half o

Re: [gentoo-dev] Make inotify a global USE flag?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21/03/13 15:14, Ulrich Mueller wrote: > Most of the time USE="foo" will enable some "foo" feature. Most of the time is not all of the time, but I see your point. Maybe "Enable inotify to notice filesystem changes". Or one of your suggestions, both

Re: [gentoo-dev] New install isos needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Making an install ISO is as pointless as writing a CMS for Gentoo.org... Gentoo should only bother if it is really necessary. ZSH-related bugs fixed ? Link SystemRescueCD : Link something else - -- Alexander alexan...@plaimi.net http://plaimi.net/~

Re: [gentoo-dev] New install isos needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 24/03/13 20:32, Ben Kohler wrote: > I really feel like we should still have an official minimal iso Feelings do not matter. - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GN

Re: [gentoo-dev] New install isos needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 24/03/13 21:17, Ben Kohler wrote: > I strongly believe it's important that we have an official install > medium [that] the official installation handbook is based [on]. I agree. Let's make it SystemRescueCd. - -- Alexander alexan...@plaimi.net h

Re: [gentoo-dev] New install isos needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 25/03/13 10:32, Tobias Klausmann wrote: > Are you saying you want to give [off-mainstream architectures] the > boot? No. > SysRescueCD does not exist for the fringe architectures. Then make it. That way we will have a reliable install medium for

Re: [gentoo-dev] New install isos needed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 25/03/13 13:20, Tobias Klausmann wrote: > On Mon, 25 Mar 2013, Alexander Berntsen wrote: >>> SysRescueCD does not exist for the fringe architectures. >> Then make it. That way we will have a reliable install medium for >>

Re: [gentoo-dev] New license: CROSSOVER-2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 28/03/13 18:42, Jeroen Roovers wrote: > diff -w helps to weed out the uninteresting whitespace changes. I also suggest app-text/wdiff. - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG

Re: [gentoo-dev] OldNet out of OpenRC: as the requester

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/04/13 01:49, Robin H. Johnson wrote: > This is NOT intended to take oldnet away from OpenRC systems at > all, but rather to encourage growth of both parts independently. For what it's worth, I think this sounds reasonable. Especially considerin

Re: [gentoo-dev] Re: devmanual moved to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/05/13 20:24, Peter Stuge wrote: > [GitHub] enforces some particular workflow You keep saying this. What do you mean? A lot of projects (including Linux) just use GitHub for hosting and nothing else. I don't see the problem. - -- Alexander ale

Re: [gentoo-dev] Re: devmanual moved to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/05/13 00:21, Peter Stuge wrote: > There is no problem if github is only used for hosting, but if it > is the primary point of contact, or if pull requests are accepted, > then github is also writing to repositories, and merge commits are > enf

Re: [gentoo-dev] Re: devmanual moved to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/05/13 08:32, Ralph Sennhauser wrote: > Once I was asked if I could look into a package. I spent a day > writing a couple of ebuilds including fixing the build system of > the target package. When I presented a first git-format-patch I was > ask

Re: [gentoo-dev] Re: devmanual moved to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/05/13 00:37, Peter Stuge wrote: >> And for the record I have not had problems with messy merges when >> commiting pull requests. > As I wrote: It works fine but doesn't scale; the mess is that you > always get a merge commit, which is usually

Re: [gentoo-dev] Re: devmanual moved to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/05/13 09:40, Ralph Sennhauser wrote: > Don't know why it would be relevant. Also I intentionally didn't > mention any names and wont do so on this list. Feel free to ask me > in private if you have a good reason. If a developer is behaving lik

Re: [gentoo-dev] Re: devmanual moved to github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/05/13 14:38, Greg KH wrote: > Linux does not use GitHub for anything, but a lot of users do use > the copy of the kernel tree on GitHub for their own development, > which has nothing to do with the main Linux kernel developer > workflow. I misr

Re: [gentoo-dev] Making systemd more accessible to "normal" users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/05/13 17:10, Luca Barbato wrote: > Those that can't use systemd: - those not using a recent linux > kernel And let's not forget those who aren't using Linux at all. - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PG

Re: [gentoo-dev] Gentoo Hangouts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I realise that by "Gentoo is and will remain Free Software"[0], what is meant is the distribution and the source code. However, I think it would be a bad example to use proprietary software for development or communication. [0]

Re: [gentoo-dev] Vanilla sources stabilization policy change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27/07/13 10:56, Chí-Thanh Christopher Nguyễn wrote: > How about dropping vanilla-sources and adding a "vanilla" USE flag > to gentoo-sources? Then we might as well just have a Linux package with a bunch of USE flags -- gentoo, hardened, libre, tu

Re: [gentoo-dev] Vanilla sources stabilization policy change

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 27/07/13 15:32, Manuel Rüger wrote: > On 07/27/2013 03:28 PM, Alexander Berntsen wrote: >> Then we might as well just have a Linux package with a bunch of >> USE flags -- gentoo, hardened, libre, tuxonice, ck, etc. > This is no

[gentoo-dev] s/disk space/drive space

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 For future reference, please use "drive space" rather than "disk space". This includes in eclasses like check-reqs. - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (GNU/Linux) Com

Re: [gentoo-dev] s/disk space/drive space

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/07/13 14:00, Michał Górny wrote: > Rationale? I don't have a disk - -- Alexander alexan...@plaimi.net http://plaimi.net/~alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.20 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http:/

Re: [gentoo-dev] s/disk space/drive space

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/07/13 14:12, Alex Legler wrote: > I don't think you're using that right. You get to make statements > "for future reference" if you actually have authority to tell > people what to do. Relax. There's even a "please" in there. > 'disk space' i

Re: [gentoo-dev] s/disk space/drive space

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/07/13 14:55, Douglas Freed wrote: >> How is it wrong? I don't have a disk so informing me that I don't have enough disk space does not make any sense.. I think my suggestion and its justification has been made clear, so I will not proceed to f

Re: [gentoo-dev] Patch to sys-apps/portage-2.2.7 giving 2% performance increase

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 19/10/13 07:38, Mike Frysinger wrote: > please send patches to gentoo-portage-...@lists.gentoo.org Just an FYI and FFR -- if your patch has a corresponding bug on bgo, please upload it there. And preferably use git format-patch. Thanks for the pa

Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/12/13 21:41, William Hubbs wrote: > My thought is to rename our "rc" to "openrc", since that would be > unique. orc is shorter and more punny (nice excuse for designing an orcish cow mascot). On 11/12/13 22:04, William Hubbs wrote:> On Wed, D

Re: [gentoo-dev] rfc: renaming "rc" binary in OpenRC

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/12/13 13:31, Samuli Suominen wrote: > orc is dev-lang/orc, with binaries like orc-bugreport That's fine. There is no binary, orc. > as said, with tab completion, orc-* would just get mixed up with > binaries from dev-lang/orc Tab-completing

Re: [gentoo-dev] Portage team, Zac's development break and stepping down as lead

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/01/14 09:39, C. Bergström wrote: > Drive-by trolling comment but I wish the effort to keep porkage > alive would have instead been directed towards pkgcore. Realistically, we have to keep updating them both in parallel. pkgcore needs to be bro

Re: [gentoo-dev] Re: [OT] pkgcore bikeshed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/01/14 12:02, Steven J. Long wrote: > Yeah but it already outshines under the hood: all you're talking > about is EAPI and radhermit is working on it; I'm sure he and > dol-sen would be happy for more help as well, so long as it's > supportiv

Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 20/01/14 18:26, William Hubbs wrote: > On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote: >> this has all been fairly ad-hoc in the past, so formalize it in >> the one place that impacts everyone -- profiles.desc. > If it is policy, s

Re: [gentoo-dev] Should we allow picture files in the Portage tree?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 13/02/14 16:12, Ulrich Mueller wrote: > Should we allow pictures if the image file format is a text file? Rather than having a hard rule for allowing or disallowing image files, we should evaluate the intention of a file. If it make sense to edit

Re: [gentoo-dev] RFC GLEP 1005: Package Tags

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 23/03/14 15:46, Jeroen Roovers wrote: > "This GLEP author would love to blight categories out of gentoo > history as a giant mistake." It does not matter. Just remove that line. It is irrelevant. - -- Alexander berna...@gentoo.org https://secur

Re: [gentoo-dev] RFC: Namespace for users created for packages

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/03/14 14:32, Michal Hrusecky wrote: > So the question is, what would you think about such a policy in > Gentoo? It would be useful. Scandinavians named Tor would likely be grateful. ;-) - -- Alexander berna...@gentoo.org https://secure.plaim

Re: [gentoo-dev] RFC: enabling ipc-sandbox & network-sandbox by default

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - -1 from me until Portage is capable of detecting if the user's operating system supports the FEATUREs, and informing them of this. I also agree with Ryan that the relevant Linux options should be added to the Gentoo Linux menu. - -- Alexander ber

  1   2   >