On Mon, 2013-05-13 at 12:02 +0100, Allan Day wrote:
Hi all,
Me, Jon and Jakub have reviewed the combined system status designs in
the attempt to address the feedback that we've got. A fresh round of
wireframes are now on the wiki [1]. I think that they resolve the most
serious issues that
showing Quit there. But I have no idea what.
Thanks for reading,
Michael Catanzaro
signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo
On Fri, 2013-07-05 at 11:08 +0100, Emmanuele Bassi wrote:
1) For applications that retain a traditional menu bar, there's
inconsistency in whether options added to the app menu are also removed
from the traditional menu.
yes. file bugs against applications that do not move them
On Sat, 2013-07-06 at 09:31 +0200, Carlos Garcia Campos wrote:
So, we either leave the
about in the window menu (it's a modal dialog of the window) or we make
the about dialog actually global and not modal.
I see your point. But I also think it's very valuable to have Help,
About, and Quit
On Sun, 2013-07-07 at 15:05 +0200, Tomasz Torcz wrote:
This seems backward. F-f-m was here first, and is still being used by some
minority (me included). Current designs break f-f-m functionality. Your
comment
about ”finding creative solutions” sounds like F-f-m was something new.
On Fri, 2013-07-05 at 11:08 +0100, Emmanuele Bassi wrote:
1) For applications that retain a traditional menu bar, there's
inconsistency in whether options added to the app menu are also removed
from the traditional menu. E.g. Gedit and Totem (3.6/3.8) removed Help,
About, and Preferences
On Wed, 2013-07-10 at 00:17 +0200, bugs wrote:
Should I file a bug?
Depends on the application and developers?
https://bugzilla.gnome.org/show_bug.cgi?id=695377
I assume that Empathy, GNOME-Calculator and so on are now aware of the
fact that the made it wrong? Maybe you can check via
On Thu, 2013-08-01 at 16:40 +0200, Matthias Clasen wrote:
For gnome-clocks, we need a new vala release.
It'd be nice if Vala did unstable releases on our release schedule.
signature.asc
Description: This is a digitally signed message part
___
On Tue, 2013-08-13 at 10:49 -0400, Matthias Clasen wrote:
Here is a first pass over bugs that are currently marked with a target
of '3.10'. The bulk of it is related to Wayland (simply because that
is where I'm focusing most, currently). If there are other bugs that
should be on this list,
On Thu, 2013-08-15 at 11:03 +0200, Alberto Ruiz wrote:
There's no intention to support pull requests or to depend in any way
in this service, this is just a nice-to-have to serve the GitHub's
community and user base.
My concern is that with no way to disable pull requests, potential
This might be harmless if there was a way to disable pull requests, but
if we mirror repos on GitHub we have a responsibility to monitor for and
accept pull requests, otherwise potential contributors who are
unfamiliar with our development flow will be discouraged when their pull
requests sit
On Sun, 2013-08-25 at 17:45 +0300, Zeeshan Ali (Khattak) wrote:
Exactly how many maintainers have shown interest in this?
fr33domlover, your passion for software freedom is admirable, but even
RMS was all in favor of GitHub until he found out that they compress
their JavaScript. (Frankly I don't
On Thu, 2013-09-05 at 14:08 +0100, Javier Jardón wrote:
- String Freeze: no string changes may be made without confirmation
from the l10n team (gnome-i18n@) and notification to both the release
team and the GDP (gnome-doc-list@).
Regarding (translatable) appdata.xml files for GNOME Software
On Mon, 2013-09-23 at 09:09 -0400, Matthias Clasen wrote:
I think that would be a great idea - could you set up the goal wiki
page and link it from the gnome-software feature ?
The goal should include that all appdata is marked for translation.
signature.asc
Description: This is a digitally
On Tue, 2013-09-24 at 10:44 +0200, Julien Blanc wrote:
I know this has been already discussed a lot, but application menu is
currently broken.
I think pretty much every point you raised is a valid problem. Some
attention is needed here at the design level.
signature.asc
Description: This is
On Thu, 2013-10-10 at 14:21 +0200, Milan Bouchet-Valat wrote:
What are you asking for exactly? To encrypt your keyring using a
password you do not need to type at all? ;-)
But he's right: autologin is useless right now, unless somehow you've
managed to never use the keyring by having no
On Thu, 2013-10-10 at 16:41 +0200, Dominique Leuenberger a.k.a. Dimstar
wrote:
Would you recommend to 'automatically' create a keyring without a
password for autologin users?
I think it's a matter of sane defaults. I do think automatic login
clearly implies that the user does not want to type
Many of our apps put Help above About in the app menu, but many put
About above Help. Many of the About labels are About app name, but
many omit the app name. Many place a separator between Help/About
(whichever is last) and Quit, but many don't.
Can we define a proper way of handling these
On Mon, 2013-11-25 at 13:35 +, Allan Day wrote:
I don't have a massively strong opinion on the label used for the
about item, or how help/about/quit should be grouped. I just went with
what feels right to me. Discussion is welcome, and all that.
I'm not sure if a strong opinion on this is
On Mon, 2013-11-25 at 14:51 +0100, Bastien Nocera wrote:
FWIW, I think that core apps shouldn't have an about menu item at all,
and it's what I've done in Totem^WVideos for example.
Maybe. It's nice to be able to see the version number, though.
signature.asc
Description: This is a digitally
On Mon, 2013-11-25 at 14:56 +0002, Yosef Or Boczko wrote:
I disagree.
We need a place with the names of the developers and the
name of the app.
Keep in mind that core is currently pretty expansive: it includes
Dictionary, Calculator, and many other apps that are widely used outside
of GNOME.
On Mon, 2013-11-25 at 14:36 +, Allan Day wrote:
In general I would say that they indicate that those items shouldn't
be in the app menu, since they are specific to a particular window or
view, but I'd be interested to hear how other people would interpret
this based on the draft
On Mon, 2013-11-25 at 19:53 +0100, Carlos Garcia Campos wrote:
and it doesn't have About because the
implementation is a modal dialog attached to a specific window.
Right, but following this logic, only Empathy would be allowed to place
About in the app menu. The revised HIG clarifies that About
On Mon, 2013-11-25 at 20:00 +0100, Carlos Garcia Campos wrote:
It's not only the version number, but additional information, for
example Epiphany shows the WebKit version, and Evince shows the
document
backend in use and its version as well.
All of which are fairly important when working on
On Mon, 2013-11-25 at 14:36 +, Allan Day wrote:
One of the goals for the new HIG is to try and avoiding spoon-feeding
people too much, and I'd prefer to avoid listing every possible thing
you might want to include in that menu. In that sense, this bug is an
interesting test case for the
On Tue, 2013-11-26 at 06:50 +0100, Rick Opper wrote:
So, an app can be kept running without any windows open then? Like on a
Mac where all windows are closed but not the app? In that case, the
app-menu would have QUIT, the window-menu would have CLOSE and SAVE, but
then which one would have
On Tue, 2013-11-26 at 10:37 +, Allan Day wrote:
The key word in the sentence you quoted was supposed to be
particular - it's supposed to mean that options that affect only one
window or view should be excluded.
That seems reasonable and it jives with what Matthias suggested. Indeed,
that
On Mon, 2013-11-25 at 13:35 +, Allan Day wrote:
Sure, that's what I've been working to do with the new HIG, which has
a page on application menus [1].
I don't have a massively strong opinion on the label used for the
about item, or how help/about/quit should be grouped. I just went with
On Tue, 2013-12-10 at 10:35 +, Allan Day wrote:
I guess I missed that one. What's the issue?
Should Quit close all open windows of the application, or only the
current window?
Say you have Epiphany open on workspace 1, and another one open on
workspace 4. If you use Quit from the app menu,
On Fri, 2014-01-03 at 23:01 +, Michael Ikey Doherty wrote:
Have it built locally. Noticed something here that I've seen in gedit
too, no doubt due to GtkSourceView. there is no automatic indentation,
i.e. hitting enter after a brace does not start a new indentation
level,
etc.
Is there a
On Sat, 2014-01-04 at 13:25 +, Michael Ikey Doherty wrote:
gedit has automatic indentation under Preferences - Editor - Tab
Stops.
Unfortunately you will wind up with indentation on your blank lines,
so
it's incompatible with projects that prohibit trailing
whitespace. :(
Yikes.
On Sat, 2014-01-04 at 15:50 -0200, Fernando Cassia wrote:
Why re-invent the wheel? You should build upon an existing, mature
IDE...
We want an IDE built with GTK+. Not only does Netbeans look bad in
GNOME, it looks bad in every other platform, as well. Something like
Geany or Anjuta would be a
On Sat, 2014-01-04 at 21:44 +0100, Reinout van Schouwen wrote:
I have no experience with either of those so won't comment on that.
But
surely aesthetics don't drive your choice of development tools?
I don't think it'd be a good idea to release a hypothetical GNOME IDE
that was not
On Sun, 2014-01-05 at 16:44 +0100, Sébastien Granjoux wrote:
What is missing?
I've been dogfooding Anjuta recently and I've been relatively impressed
with its potential. I think the plugin-based system is its biggest
strength: I want to be able to use the same environment for all of my
On Sun, 2014-01-05 at 18:03 +0100, Sébastien Wilmet wrote:
Having both gedit and Anjuta is already a duplication of effort.
Personally I prefer only a text editor, and use the command line or
other applications for the other features (git, glade, devhelp, etc).
Many developers prefer this
On Sun, 2014-01-05 at 19:31 +0100, Sébastien Granjoux wrote:
But some functions are really
useful, like saving all files before compiling or setting breakpoints
in
the text view.
Anjuta's gdb plugin is really an excellent feature, by the way.
Sometimes the breakpoints you have set disappear
On Wed, 2014-02-05 at 15:40 -0500, Jasper St. Pierre wrote:
(Red Hat does not make over a billion dollars a year. The billion
dollars was profits, not revenue. We're still a fairly small company
operating on tight margins)
Vice versa, I presume.
signature.asc
Description: This is a digitally
Can I add this Sushi bug:
https://bugzilla.gnome.org/show_bug.cgi?id=704243
signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
On Mon, 2014-02-24 at 19:43 -0500, Joanmarie Diggs wrote:
Related 2: Accerciser was pretty broken, but Javi fixed the more
critical of those bugs in master.
Any chance of a 3.10 release soon? The latest version is 3.8.2.
I also hope [1] receives some attention.
I want to be concerned about
On Wed, 2014-03-05 at 20:15 +, João Martins wrote:
Hi
I saw Four-in-a-row For-in-a-row Al in gnome GSOC ideas list and i
thinks this is a challenging and interesting idea , want to know if is
possible i participe in this project?
Hey João,
You'll notice on the ideas page, there is a tag
On Sun, 2014-04-13 at 13:54 -0700, Sriram Ramkrishna wrote:
How do we solve this?
Let's start with an actual set of metrics that is accurate. If there
is an issue and certainly if you care about it, we have a team called
the bug squad who can look into it. We solve these problems by
On Mon, 2014-04-14 at 01:33 +0200, Andre Klapper wrote:
On Sun, 2014-04-13 at 16:31 -0500, Michael Catanzaro wrote:
There's merit in his complaint.
or her.
andre
Yes, my apologies.
signature.asc
Description: This is a digitally signed message part
On Tue, 2014-04-29 at 06:19 -0400, Matthias Clasen wrote:
The end goal here is to have GTK+ depend on a 'complete' icon theme,
so that you can assume that the naming spec is covered, in both full
color and symbolic versions, regardless of which platform you are
using GTK+ on.
That is [1],
On Sat, 2014-08-02 at 00:22 +0200, Andre Klapper wrote:
A first list of blockers and potential blockers for the upcoming
release, based on data in GNOME Bugzilla. Note that there are lots of
gnome-themes-standard/HighContrast tickets open.
Please take a quick look at the list below, comment
On Sat, 2014-08-02 at 14:14 +0200, Zeeshan Ali (Khattak) wrote:
You mean send them email to not push translations? Are they all on
those lists and read their inbox each time before pushing changes? If
so, sure but then again the main issue (at least for me) is forgetting
(to run `git push
On Sat, 2014-08-02 at 00:22 +0200, Andre Klapper wrote:
Please take a quick look at the list below, comment (on the ticket),
and
raise your voice if you see an important issue missing.
https://bugzilla.gnome.org/show_bug.cgi?id=728496 is getting really
annoying as well.
signature.asc
On Sun, 2014-08-03 at 11:14 +0200, scl wrote:
Indeed.
I wanted to be precise and listed 'Shell Command Language' and 'M4'.
Now that I see how the Owner row breaks the layout, I'm hesitating
whether we want to list them, because presumably every GNOME project
uses the Autotools which include
On Sun, 2014-08-03 at 08:05 +0200, scl wrote:
remote: ERROR: babl.doap is not valid:
remote:doap:category property should be one of:
apps,core,core-apps,deprecated,infrastructure
Er, so what category does babl belong in? I'm pretty sure it's not
core, but it's the only plausible choice
On Wed, 2014-08-06 at 15:31 +0200, Sébastien Wilmet wrote:
Er, so what category does babl belong in? I'm pretty sure it's not
core, but it's the only plausible choice here.
I think if you don't mention any category it'll go to the other
category.
OK, that seems best for babl.
On Wed, 2014-08-06 at 15:09 +0200, Andre Klapper wrote:
In jhbuild's moduleset definitions it's currently listed in:
https://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-apps-3.14.modules
andre
The problem is that there are modules in gnome-apps, like babl, that are
not apps, but just
On Wed, 2014-08-06 at 21:53 +0200, scl wrote:
Hi,
thank you for your answers.
I've removed now the M4 language item from the Babl
description and also removed the category. Now it
is filed under 'Not part of a suite'. From my recent
experiences I assumed we now have *only* the categories
On Tue, 2014-08-12 at 18:32 +0200, Andre Klapper wrote:
Thanks everybody for cleaning up last week's list by fixing and
reassassing quite some items!
There are only eight items left marked as blockers:
Can we please add https://bugzilla.gnome.org/show_bug.cgi?id=683266 --
this is needed for
On Sun, 2014-08-03 at 01:33 +0200, Olav Vitters wrote:
1. New categories: Core, Core Apps, Apps
Note: Not every module has been put into right category. If you
spot
errors, please let release-t...@gnome.org know. I'm planning to add
some cross checks in the release team scripts to
On Sun, 2014-08-24 at 21:18 +0200, Andre Klapper wrote:
All user comments seem to be about 3.10 but none about 3.12 (yet)? Is
there any indication that this is still a problem in 3.12/3.13 code?
In any case, a comment by a g-o-a maintainer would be extremely
welcome
on that ticket (if g-o-a
On Fri, 2014-08-22 at 08:47 +0100, Allan Day wrote:
Hi all,
A new version of the HIG is in the works, to be released along with
GNOME 3.14 [1]. I'm currently looking for feedback.
I'm about halfway done reading. I have a few suggestions, all minor:
* The Visual Layout page discusses how
On Tue, 2014-08-12 at 18:32 +0200, Andre Klapper wrote:
Thanks everybody for cleaning up last week's list by fixing and
reassassing quite some items!
There are only eight items left marked as blockers:
This one should be removed from the blockers list:
On Sun, 2014-08-31 at 15:25 -0700, Sriram Ramkrishna wrote:
Well it seems that is there. It would be nice to get some support for
GtkHeaderBar in glade. Barring that, let's at least see some
documentation in developer.gnome.org for javascript and vala. Right
now, it doesn't exist. I found
On Tue, 2014-09-02 at 14:43 +0200, Gian Mario Tagliaretti wrote:
in a previous post you mentioned outdated python examples, can you
point it out? I had a quick look (maybe too quick) but it looks to me
that the examples use the introspected bindings already.
Here:
On Tue, 2014-09-02 at 08:57 -0700, Germán Poo-Caamaño wrote:
As far as I see, the same applies for every language. None of them
has
GtkHeaderBar, though it does not mean than everything else is wrong or
outdated, it's just incomplete.
Of the two pages I checked in platform-overview, both
On Thu, 2014-09-04 at 14:46 +0100, Allan Day wrote:
Fred's done a
fantastic job keeping library.gnome.org going, but we probably need
something else (or at least major improvements).
I did not know this existed!
signature.asc
Description: This is a digitally signed message part
On the buttons page:
When several buttons are placed next to each other, ensure that they
have the same width. This is particularly important for pairs of Cancel
and OK buttons.
And then:
Often this will be the OK or equivalent button.
And then:
Label all buttons with imperative verbs
But if
Hi Allan,
I have a bit more feedback on the HIG.
On the header bar page: Header bars are incompatible with menu bars.
On the menu bar page: menu bars can still be an appropriate choice,
particularly for applications that already incorporate a header
bar. (So that's a contradiction.)
The menu
On Wed, 2014-09-17 at 12:02 +0100, Allan Day wrote:
Dynamic tabs always have equal widths, fixed tabs don't - which is
what you're referencing here. I've tried to make it a bit clearer, but
let me know if you think it's problematic still.
Looks good! One more question: should we use GtkStack
On Tue, 2014-09-23 at 16:08 +0200, Sébastien Wilmet wrote:
As a related matter, it seems that the GNOME Goals don't have a lot of
success.
Related, but separate. The problem is not so much slow adoption of old
goals, but lack of approval for new ones. Header bars are still an
unapproved goal
On Tue, 2014-09-23 at 20:24 +0200, Daniel Mustieles García wrote:
About this, I have a question... existing modules are easily
tracked, and can check if they fit the goals but, what happens with
new modules? When a developer creates a new module, is he/she advised
to review and apply the
On Tue, 2014-09-23 at 14:17 -0400, Matthias Clasen wrote:
I think this is a great idea. When we discussed this at Guadec, I got
the impression that we should use this to draw attention to
longstanding UX annoyances, early enough in the cycle to address them.
Yes, improving the quality of the
On Wed, 2014-10-08 at 08:59 +0200, Juan Rafael García Blanco wrote:
I dare to propose myself for maintainer. I have almost no experience
in maintenance (I maintain libchamplainmm, which doesn't count);
Looks like you already have a git account and know how to handle
releases, and have also
On Thu, 2014-10-09 at 22:33 +0200, Juan R. García Blanco wrote:
Hi,
Yes, I do! If you agree, I'll wait until Sunday to make that release.
Right now I do not have any questions. I have never uploaded a tarball
to the ftp, though. I will for sure let you know if I any question
comes
to my
On Tue, 2014-10-14 at 14:44 -0400, Matthias Clasen wrote:
On Tue, Oct 14, 2014 at 1:47 PM, Jim Nelson j...@yorba.org wrote:
It would be great if the DOM was available via WebKitGTK and the local
library did the IPC for us, but I've been told that that's not going
to happen. The DOM is a
On Wed, 2014-10-15 at 18:36 +0200, Carlos Garcia Campos wrote:
The current epiphany code was supposed to be a temporary solution, the
idea was to use a private dbus connection instead of using the session
bus, but in the end we never found the time to do that.
Christian Hergert suggested
On Sat, 2014-10-18 at 00:54 +0100, Magdalen Berns wrote:
Quick new maintainer question about this (apologies if it's the wrong
list!): I made a new release and I just want to check I am doing it
right.[1]
How do I tag the releases on git.gnome.org
git tag -a JAVA_ATK_WRAPPER_0_30_6
git
On Sat, 2014-11-01 at 14:14 +0100, Paul Geisler wrote:
if I modify a service that is controlled by dbus, like eg.
'indicator-datetime-service', build and install it, where can I get
access to it's stderr / stdout messages, like those issued by using
g_warning and other glib logging
On Sun, 2014-11-23 at 22:32 +0100, Damian Ivanov wrote:
Hello,
Looking at the screenshot
@https://wiki.gnome.org/ThreePointFifteen/Features/Taquin /
https://people.gnome.org/~mcatanzaro/gnome-taquin.png
the start over button there is a bit odd / out of place.
Would't it be better on
On Tue, Feb 3, 2015 at 3:52 AM, Ryan Lortie de...@desrt.ca wrote:
hi,
On Mon, Feb 2, 2015, at 10:10, Michael Catanzaro wrote:
FWIW, if you run devhelp with jhbuild, you will get documentation
for
the version of the library in jhbuild.
This is only true if the docs are actually built
On Thu, Jan 29, 2015 at 2:04 PM, Erick Pérez Castellanos
eric...@gnome.org wrote:
My idea was to have them (the app, which provides search at the same
time) running all the time in the background, but that feels like
using the resources of the CPU without the user knowing
That is what GNOME
Hi,
On Mon, Jan 5, 2015 at 8:01 AM, Yosef Or Boczko yosef...@gnome.org
wrote:
E.g., I think it is not right for the scoreboard to be a tiny
GtkLabel
in the header bar.
Putting the score in the header bar is actually pretty typical for us.
I would prepend Score: to the label, and take
On Fri, Jan 9, 2015 at 3:10 PM, Juan R. juanr...@gmail.com wrote:
Hi,
I just noticed there exists a libgames-scores library; however I do
not
see any game depending on it yet. Is it usable already?
Thank you. Regards,
Juan.
It's almost ready; at least, it's in a good enough state for GNOME
On Fri, Jan 9, 2015 at 7:38 AM, Allan Day allanp...@gmail.com wrote:
The Restore Disk Image... label is a bit misleading there (you're
not always restoring). I wonder if it should be changed...
Allan
Yes, that is a problem. Let's fix it. Any suggestions for this label?
How about Write Disk
On Fri, Feb 13, 2015 at 9:51 AM, Olav Vitters o...@vitters.nl wrote:
With Bugzilla 4.4 we can disable UNCONFIRMED on a per-product basis.
With that option available, I suggest to kill off the UNCONFIRMED
status
for all products except whomever wants it.
This would be highly desirable. Bonus
In particular, we should identify material from the HowDoI/Jhbuild page
(which conflicts with the guidance on the BuildGnome page) that we want
to keep, and merge it into the BuildGnome page. We should not have
competing pages with competing advice; it's way too confusing for
newcomers.
On Thu, 2015-03-19 at 09:54 -0400, Michael Hill wrote:
On Thu, Mar 19, 2015 at 9:11 AM, Michael Catanzaro
mcatanz...@gnome.org wrote:
Having multiple conflicting tutorials is confusing to new
contributors,
and harmful when those two tutorials are incompatible
On Thu, 2015-03-19 at 07:17 -0400, Carlos Soriano Sanchez wrote:
I finished, and I linked BuildGnome on GnomeLove as the *official*
guide.
One month after that Ryan Lortie write a full jhbuild guide in
HowDoI/Jhbuild because he thought there were no guide for jhbuild!
He is a experienced
On Thu, 2015-03-19 at 13:42 +0100, Andres G. Aragoneses wrote:
On 17/03/15 13:33, Carlos Soriano Sanchez wrote:
Hi,
So after some work in GnomeLove and discussions in the gnome-love list, I
would like to make this proposal.
Read more here
On Mon, Feb 23, 2015 at 1:22 PM, Andres G. Aragoneses
kno...@gmail.com wrote:
Ok but my suggestion about OPEN remains.
UNCONFIRMED-OPEN doesn't look too confusing.
UNCONFIRMED/NEW - UNRESOLVED would be my suggestion.
___
desktop-devel-list mailing
Hi,
Currently, half our apps use nice symbolic icons in the app menu,
while the other half use shrunken hicolor icons. This inconsistency is
a poor user experience, and not something that should happen in a
serious operating system. Progress is being tracked at [1] under the
column 3.16
Oops, I meant to send this to
desk...@lists.fedoraproject.org. Um, whatever, it's relevant to this
list too. :)
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
On Wed, 2015-04-29 at 13:04 +0200, Sébastien Wilmet wrote:
Hi Javier,
On Wed, Apr 29, 2015 at 11:48:01AM +0100, Javier Jardón wrote:
Only a quick reminder that 3.17.1 is scheduled for today [1]
I noticed that quite a few of modules have not been updated, so it
would be great if you can
On Tue, 2015-05-05 at 18:54 -0500, alexskc wrote:
I usually read a CONTRIBUTING.md before I make any contributions so
that
I make sure I'm doing it right.
Er good point, I seriously forgot that people might actually open the
file and see what's inside. New proposal:
The GNOME contributing
On Tue, 2015-05-05 at 13:44 -0400, Colin Walters wrote:
I'm certainly cognizant of issues such as github not being FOSS,
the inconsistency with other projects hosted in GNOME, but
with the current status quo, if the choice is between don't use PRs
or don't be in GNOME infra that's likely going
On Tue, 2015-05-05 at 18:51 +0200, Andrea Veri wrote:
The GNOME contributing guidelines do require patches to be
forwarded to GNOME's Bugzilla instance hosted at
https://bugzilla.gnome.org, as such please do not open Pull Requests
(PRs) against any of the modules under the GNOME organization
On Sat, 2015-04-04 at 19:45 +0100, Emmanuele Bassi wrote:
Leaving tablets aside, I honestly don't see the difference between the
desktop and laptop use cases. You can access the overview using the
Super/Windows/Command key on your keyboard, or using the hot corner at
the top-left. You can also
On Mon, 2015-06-22 at 16:36 +0100, Philip Withnall wrote:
Do we require automake 1.13 though?
Looks like it was released January 1, 2013... so we should.
Automake 2.0 isn’t out yet (though
it looks cool), so I’d be tempted to leave in the ACLOCAL_AMFLAGS
recommendation for backwards
On Tue, 2015-06-23 at 08:33 +0100, Philip Withnall wrote:
As Kalev says, we should ensure this still builds with various
distros.
RHEL7 is fine. Debian stable (Jessie) has 1.14. Fedora has had ≥ 1.13
for a long time. Arch has 1.15. FreeBSD has 1.15.
So unless anybody objects, I think a
On Wed, 2015-06-24 at 08:56 +0100, Emmanuele Bassi wrote:
I do hope that, if you're using glib-gettext or intltool, you spend a
little bit of time to port to upstream gettext instead.
Has anyone written a guide on how to do this?
I thought intltool was preferred. We definitely need better
On Wed, 2015-06-24 at 09:21 +0100, Philip Withnall wrote:
libtoolize complains about it:
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in
Makefile.am.
But I guess libtoolize is wrong.
Is there an upstream bug report?
No need. I have libtool 2.4.2 provided by Fedora 22,
On Wed, 2015-06-24 at 14:17 +0100, Emmanuele Bassi wrote:
Sadly, it's still in use for AppData XML, but for that (and any other
XML-based format) there's itstool, which is also used by the
documentation team for the application help:
http://itstool.org/
I will wait for someone to replace
This is a nit, but I think the 'set -x' to 'set +x' at the end of the
sample autogen.sh is too expansive, since it results in the conditional
tests being printed as independent statements:
autoreconf: Leaving directory `.'
+ '[' '' = '' ']'
+ ./configure --prefix /home/mcatanzaro/jhbuild/install
On Sat, 2015-05-30 at 08:09 -0500, Michael Catanzaro wrote:
This is a nit, but I think the 'set -x' to 'set +x' at the end of the
sample autogen.sh is too expansive, since it results in the
conditional
tests being printed as independent statements:
Another problem is that the 'set +x' gets
On Sun, 2015-08-16 at 11:31 +0200, Sébastien Wilmet wrote:
--install has been added to the ACLOCAL_AMFLAGS.
You don't want to touch that (in Makefile.am) anymore; see:
https://mail.gnome.org/archives/desktop-devel-list/2015-June/msg9.h
tml
On Sat, 2015-08-22 at 10:45 +0200, Sébastien Wilmet wrote:
On Fri, Aug 21, 2015 at 04:18:09PM -0500, Michael Catanzaro wrote:
On Sun, 2015-08-16 at 11:31 +0200, Sébastien Wilmet wrote:
--install has been added to the ACLOCAL_AMFLAGS.
You don't want to touch that (in Makefile.am) anymore
1 - 100 of 383 matches
Mail list logo
