Hi there
Next meeting will happen tonigh on #mageia-dev at 20h UTC.
Here are our topics:
- Review of build system and distro bootstrap
- Proposal for mentoring process (wiki page will be updated today):
review and comments
- Review on current mentoring process and people concerned
- Review on
2011/1/19 Michael scherer m...@zarb.org:
Because that would 1) requires a patch to rpm that we do not have or
2) patch all python packages to had %ghost on all *.pyc, and do a
compilation of
*pyc ( the 2nd part is easy, the first one is slightly harder to automate )
3) do not care about
On Wed, 19 Jan 2011 08:25:23 +0100
Michael scherer m...@zarb.org wrote:
I'm not sure about twice the work: you don't need to track twice the
software releases (except for the interpreter itself), or twice the
upstream patches, etc.
Well, if we handle this like 2 separates languages,
Hi,
I'd like to move away from the hardcoded backgrounds location for
themes, and put them in a distro-neutral path
(was /usr/share/mdk/backgrounds/ in Mandriva)
Most Gnome backgrounds appear to be located in
/usr/share/pixmaps/backgrounds/ (some are in /usr/share/backgrounds/)
Is everyone ok
Donald Stewart
On 19 January 2011 12:06, Olivier Blin mag...@blino.org wrote:
Hi,
I'd like to move away from the hardcoded backgrounds location for
themes, and put them in a distro-neutral path
(was /usr/share/mdk/backgrounds/ in Mandriva)
Most Gnome backgrounds appear to be located in
On 15 January 2011 12:08, Remy CLOUARD shikam...@mandriva.org wrote:
Hi there,
I just imported the RPM Spec File Syntax page in the wiki.
It’s located here: http://mageia.org/wiki/doku.php?id=spec_syntax
Please review this page as it’s one of the most important one for the
beginning of the
On 17 January 2011 23:53, Florian Hubold doktor5...@arcor.de wrote:
Am 15.01.2011 11:08, schrieb Remy CLOUARD:
http://mageia.org/wiki/doku.php?id=spec_syntax
Please review this page as it’s one of the most important one for the
beginning of the mentoring process, with the RPM Howto page (yet
On 19 January 2011 15:02, Olivier Blin mag...@blino.org wrote:
Remy CLOUARD shikam...@mandriva.org writes:
On Wed, Jan 19, 2011 at 01:06:49PM +0100, Olivier Blin wrote:
I'd like to move away from the hardcoded backgrounds location for
themes, and put them in a distro-neutral path
(was
On Wed, Jan 19, 2011 at 02:44:35PM +0200, Ahmad Samir wrote:
On 15 January 2011 12:08, Remy CLOUARD shikam...@mandriva.org wrote:
Hi there,
I just imported the RPM Spec File Syntax page in the wiki.
It’s located here: http://mageia.org/wiki/doku.php?id=spec_syntax
Please review this
Michael scherer skrev 19.1.2011 15:30:
On Wed, Jan 19, 2011 at 02:44:35PM +0200, Ahmad Samir wrote:
On 15 January 2011 12:08, Remy CLOUARDshikam...@mandriva.org wrote:
Hi there,
I just imported the RPM Spec File Syntax page in the wiki.
It’s located here:
1. Leave them where they are for now (breaks less things) and
2. pursue standardization with freedesktop.org, then
3. adopt that standard.
Done in three.
--
Hoyt
Hoyt Duff hoytd...@gmail.com writes:
1. Leave them where they are for now (breaks less things) and
2. pursue standardization with freedesktop.org, then
3. adopt that standard.
Done in three.
I wouldn't want to keep a path with mdk inside, even temporarily
--
Olivier Blin - blino
I understand your sentiment. Given unlimited resources, it is an
acceptable choice.
I'm not advocating ignoring it. Nor am I saying it should continue
unabated. I'm advocating a way to 'solve' the problem on a long-term
basis with a minimum of hassle.
As a matter of expediency, it does no harm
On 19.01.2011 02:12, Michael scherer wrote:
Hi,
I will not be present at the packagers's meeting tonight, as
I will likely be finishing the app installer meeting in
Nuremberg ( transalte : discuss in a pub ).
The wifi is expensive, and so I had to use ninja
powers to get ssh access (
Ahmad Samir ahmadsamir3...@gmail.com writes:
I'd like to move away from the hardcoded backgrounds location for
themes, and put them in a distro-neutral path
(was /usr/share/mdk/backgrounds/ in Mandriva)
Most Gnome backgrounds appear to be located in
/usr/share/pixmaps/backgrounds/ (some are
Actually, /usr/share/backgrounds seems pretty good, since
gnome-control-center uses this directory by default
I'll use this one temporarily.
--
Olivier Blin - blino
Then can KDE be patched to look there, packaging complimentary
backgrounds will be far simpler then, 4 packages can be merged
I was looking to help and found spec-helper to be (hopefully) one of the
easier ones left:
- there's still some java stuff, which i assume dmorgan (and hopefully some
help) is going to take care of.
- there's rpm stuff
- and seemingly alot of duplicates in mdv and mga list.
so, this one was
On Mon, Jan 10, 2011 at 01:49:30AM +0100, Michael Scherer wrote:
Le vendredi 07 janvier 2011 à 23:45 +0100, Remy CLOUARD a écrit :
You can find the page here:
http://wiki.mandriva.com/en/Policies/Ruby
[...]
This cause problem since we do have rpm present twice ( without people
noticing, as
http://svn.mageia.org/soft-cleaning/status.html#monitor-edid
says - README: Some reference to the Mandriva mailing list and
bugzilla will need to be changed to Mageia ones
Do we really want to?
What is the point?
I think we can package this tool as-is, as a tool provided by Mandriva
like if we
On Wed, 19 Jan 2011, Pascal Terjan wrote:
http://svn.mageia.org/soft-cleaning/status.html#monitor-edid
says - README: Some reference to the Mandriva mailing list and
bugzilla will need to be changed to Mageia ones
Do we really want to?
What is the point?
I think we can package this tool
If someday it becomes unmaintained or for any other reason, we can
fork it, but currently I think of it as an external tool and see no
reason in importing it into our svn
Do you mean to avoid importing the source code to modify it?
If so, i agree, we can just import it as source package like
2011/1/19 Angelo Naselli anase...@linux.it:
If someday it becomes unmaintained or for any other reason, we can
fork it, but currently I think of it as an external tool and see no
reason in importing it into our svn
Do you mean to avoid importing the source code to modify it?
If so, i agree,
Op woensdag 19 januari 2011 21:32:13 schreef Pascal Terjan:
http://svn.mageia.org/soft-cleaning/status.html#monitor-edid
says - README: Some reference to the Mandriva mailing list and
bugzilla will need to be changed to Mageia ones
Do we really want to?
What is the point?
I think we can
On Wed, Jan 19, 2011 at 21:13, Angelo Naselli anase...@linux.it wrote:
If someday it becomes unmaintained or for any other reason, we can
fork it, but currently I think of it as an external tool and see no
reason in importing it into our svn
Do you mean to avoid importing the source code to
On Wed, Jan 19, 2011 at 21:33, Maarten Vanraes
maarten.vanr...@gmail.com wrote:
Op woensdag 19 januari 2011 21:32:13 schreef Pascal Terjan:
http://svn.mageia.org/soft-cleaning/status.html#monitor-edid
says - README: Some reference to the Mandriva mailing list and
bugzilla will need to be
Maarten Vanraes maarten.vanr...@gmail.com writes:
except, is spec-helper one of the patches ones too?
Buildrequires will have to be changed to perl(IPC::Run3) instead of
perl(IPC::Run), so my question is:
Do i patch this to run with IPC::Run3 ? or is this to be forked?
Why can't you keep
Op woensdag 19 januari 2011 23:33:10 schreef Olivier Blin:
Maarten Vanraes maarten.vanr...@gmail.com writes:
except, is spec-helper one of the patches ones too?
Buildrequires will have to be changed to perl(IPC::Run3) instead of
perl(IPC::Run), so my question is:
Do i patch this to
Maarten Vanraes maarten.vanr...@gmail.com writes:
Op woensdag 19 januari 2011 23:33:10 schreef Olivier Blin:
Maarten Vanraes maarten.vanr...@gmail.com writes:
except, is spec-helper one of the patches ones too?
Buildrequires will have to be changed to perl(IPC::Run3) instead of
On Wed, 19 Jan 2011 13:53:08 +0100, Remy CLOUARD shikam...@mandriva.org wrote:
On Wed, Jan 19, 2011 at 01:06:49PM +0100, Olivier Blin wrote:
Hi,
I'd like to move away from the hardcoded backgrounds location for
themes, and put them in a distro-neutral path
(was
29 matches
Mail list logo
