-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Check out Linphone. Works well to Mac OS X and Microsoft Windows in my
experience. The interface is not great, but several non-technical
users have been able to use it to talk to me, so it can't be that bad
while we're waiting for Tox to mature.
Hello,
On Sun, 07 Sep 2014 17:51:46 +0200 J. Roeleveld wrote:
It probably works, provided all your contacts also use it.
As long as the vast majority of my contacts use Skype and Yahoo, I will not
be able to switch. If Kopete (and other generic IM clients) would add
support for tox, then it
On 08/09/14 06:47, Rick Zero_Chaos Farina wrote:
On 09/07/2014 09:03 PM, Rich Freeman wrote:
Right now the general policy is that we don't allow unmasked (hard or
via keywords) ebuilds in the tree if they use an scm to fetch their
sources. There are a bunch of reasons for this, and for the
Samuli Suominen:
On 08/09/14 06:47, Rick Zero_Chaos Farina wrote:
On 09/07/2014 09:03 PM, Rich Freeman wrote:
Right now the general policy is that we don't allow unmasked (hard or
via keywords) ebuilds in the tree if they use an scm to fetch their
sources. There are a bunch of reasons for
Dnia 2014-09-09, o godz. 17:41:27
hasufell hasuf...@gentoo.org napisał(a):
Samuli Suominen:
On 08/09/14 06:47, Rick Zero_Chaos Farina wrote:
On 09/07/2014 09:03 PM, Rich Freeman wrote:
Right now the general policy is that we don't allow unmasked (hard or
via keywords) ebuilds in the
Michał Górny:
Dnia 2014-09-09, o godz. 17:41:27
hasufell hasuf...@gentoo.org napisał(a):
Samuli Suominen:
On 08/09/14 06:47, Rick Zero_Chaos Farina wrote:
On 09/07/2014 09:03 PM, Rich Freeman wrote:
Right now the general policy is that we don't allow unmasked (hard or
via keywords)
Dnia 2014-09-09, o godz. 17:58:17
hasufell hasuf...@gentoo.org napisał(a):
Michał Górny:
Dnia 2014-09-09, o godz. 17:41:27
hasufell hasuf...@gentoo.org napisał(a):
Samuli Suominen:
On 08/09/14 06:47, Rick Zero_Chaos Farina wrote:
On 09/07/2014 09:03 PM, Rich Freeman wrote:
Right
On Tue, Sep 9, 2014 at 2:16 PM, Michał Górny mgo...@gentoo.org wrote:
Dnia 2014-09-09, o godz. 17:58:17
hasufell hasuf...@gentoo.org napisał(a):
Michał Górny:
Dnia 2014-09-09, o godz. 17:41:27
hasufell hasuf...@gentoo.org napisał(a):
Samuli Suominen:
On 08/09/14 06:47, Rick
On Mon, Sep 8, 2014 at 2:59 AM, Ulrich Mueller u...@gentoo.org wrote:
What is the problem with making snapshot of some git commit and
placing it on mirrors?
To be clear, there isn't one. The more typical approach for fixes is
to use the upstream main release tarball and continue to provide
Michał Górny:
And how can you test a VCS ebuild? You can't assume upstream will be
stuck on one commit.
I don't see the argument. It sounds like you are saying one day,
upstream might stop supporting architecture xy, so better we just omit
all of them from KEYWORDS. Err?
For example, I
Dnia 2014-09-07, o godz. 21:03:00
Rich Freeman ri...@gentoo.org napisał(a):
Right now the general policy is that we don't allow unmasked (hard or
via keywords) ebuilds in the tree if they use an scm to fetch their
sources. There are a bunch of reasons for this, and for the most part
they
Hi,
09.09.14 20:36, hasufell написав(ла):
Michał Górny:
And how can you test a VCS ebuild? You can't assume upstream will be
stuck on one commit.
I don't see the argument. It sounds like you are saying one day,
upstream might stop supporting architecture xy, so better we just omit
all
Jauhien Piatlicki:
When I accept ~arch I expect that no live ebuilds will be built. I think
other gentoo users expect the same.
Just because users are used to it doesn't make it better.
Emerging live ebuild usually is quite a risky thing, so hiding such stuff
behind dropped keywords is
Hello,
Let's keep it short: I think herds don't serve any special purpose
nowadays. Their existence is mostly resulting in lack of consistency
and inconveniences.
In particular:
1. We have two different tags in metadata.xml that serve a similar
purpose -- herd/ and maintainer/, with herd/ being
On Tue, Sep 9, 2014 at 3:45 PM, Michał Górny mgo...@gentoo.org wrote:
Let's keep it short: I think herds don't serve any special purpose
nowadays. Their existence is mostly resulting in lack of consistency
and inconveniences.
The original design was that packages belong to herds, and
On 09/09/14 15:56, Rich Freeman wrote:
On Tue, Sep 9, 2014 at 3:45 PM, Michał Górny mgo...@gentoo.org wrote:
Let's keep it short: I think herds don't serve any special purpose
nowadays. Their existence is mostly resulting in lack of consistency
and inconveniences.
The original design was that
Dnia 2014-09-09, o godz. 16:46:29
Anthony G. Basile bluen...@gentoo.org napisał(a):
On 09/09/14 15:56, Rich Freeman wrote:
On Tue, Sep 9, 2014 at 3:45 PM, Michał Górny mgo...@gentoo.org wrote:
Let's keep it short: I think herds don't serve any special purpose
nowadays. Their existence is
On 10 September 2014 10:23, Michał Górny mgo...@gentoo.org wrote:
I don't understand your concern. I'm only saying we should stop relying
on that stupid out-of-repository herds.xml file and put the e-mail
address directly in metadata.xml. Bugzilla and bug assignment would
work pretty much the
On Wed, Sep 03, 2014 at 03:27:15PM -0400, Rich Freeman wrote:
On Wed, Sep 3, 2014 at 2:11 PM, William Hubbs willi...@gentoo.org wrote:
I can deprecate it. To do so, I would need to have it print out a
deprecation warning that would be wrong for Gentoo in the next release.
That warning
On Tuesday, September 09, 2014 08:59:41 PM Andrew Savchenko wrote:
My last response to this, as it is getting too OT
Hello,
On Sun, 07 Sep 2014 17:51:46 +0200 J. Roeleveld wrote:
It probably works, provided all your contacts also use it.
As long as the vast majority of my contacts use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm not familiar with the formalities surrounding ebuild commit
messages -- is this something that's actually mandatory? If not, is
this change at least mandated? If not, this should probably go to QA
before Portage.
- --
Alexander
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/09/14 05:22, Brian Dolbec wrote:
LGTM
+1
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
Dnia 2014-09-08, o godz. 13:32:03
Jauhien Piatlicki jauh...@gentoo.org napisał(a):
can repoman logic be changed a little bit, so it prepends commit message
for git repos with package name? Otherwise git log when using repoman
looks not informative.
You can use app-shells/repo-commit. It also
This next meeting is to decide which of all the recent patches and
bugfixes should go into a release I hope to do this weekend.
Next meeting: Thursday Sept. 11, 2014 20:00 UTC
2014-09-11T20:00:00 UTC (ISO 8601)
Agenda: 2.2.13 release patch inclusion/review
So, please try to be prepared with
On 09/09/2014 12:12 AM, Alexander Berntsen wrote:
On 09/09/14 05:22, Brian Dolbec wrote:
LGTM
+1
Thanks!
Pushed as commit afe9939fc89927346806e8013535bcc15688cb69.
--
Thanks,
Zac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, 08 Sep 2014 09:56:59 +0200
Alexander Berntsen berna...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
LGTM.
- --
Alexander
berna...@gentoo.org
+1, commit
- --
Brian Dolbec dolsen
-BEGIN PGP
26 matches
Mail list logo
