On Wed, Nov 25, 2009 at 07:06:02PM +0100, Fryderyk Dziarmagowski wrote:
> On Wed, 25 Nov 2009 17:43:38 +0100
> sparky wrote:
>
> > Author: sparky Date: Wed Nov 25 16:43:38 2009 GMT
> > Module: packages Tag: HEAD
> > Log message:
> > - BR: GConf2, GC
On Wed, 25 Nov 2009 17:43:38 +0100
sparky wrote:
> Author: sparky Date: Wed Nov 25 16:43:38 2009 GMT
> Module: packages Tag: HEAD
> Log message:
> - BR: GConf2, GConf2-devel, curl-devel, gnome-power-manager, pulseaudio, which
What is the idea behin
> Why don't we just update all specs on HEAD and DEVEL using some
> automagic awk script? If Provides work it should works too.
I'm not an awk-guru :)
Zsolt
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailm
On Wed, 25 Nov 2009, Zsolt Udvari wrote:
> > i update git-core.spec, i don't know a sh*t of tetex* crapolla. so i
> > just disable the doc building then? i care for git-core as a program,
> > not the madness behind documentation building. so i as git-core
> > updater don't now anything which tetex
> i update git-core.spec, i don't know a sh*t of tetex* crapolla. so i
> just disable the doc building then? i care for git-core as a program,
> not the madness behind documentation building. so i as git-core
> updater don't now anything which tetex is needed or is needed not
> whatsoever.
Ask me
On Wednesday 25 November 2009 18:02:50 Zsolt Udvari wrote:
> > isn't this this is too complicated for average developer (tm)?
>
> Hm? I don't understand you. If a developer ("package maintainer")
> updates and cares about foo.spec, (s)he knows that this package needs
> or not any tetex-package.
i
> > From the "developers": I want that the package "maintainers" check
> > his/her packages and their (build)requires and if necessary, update
> > the depends from tetex to texlive and increment the release (and
> > test the package, of course ;))
> >
> > From the "users" (and "developers" too ;)):
On Wednesday 25 November 2009 10:51:15 Zsolt Udvari wrote:
> So, what I want?
>
> From the "developers": I want that the package "maintainers" check
> his/her packages and their (build)requires and if necessary, update
> the depends from tetex to texlive and increment the release (and test
> the pa
On Wednesday 25 November 2009 14:16:18 Patryk Zawadzki wrote:
> 2009/11/25 Elan Ruusamäe :
> > On Wednesday 25 November 2009 11:36:38 Patryk Zawadzki wrote:
> >> Switch to git / mercurial already? *hides*
> >
> > i'd see first git.pld-linux.org operating for the developer community
> > first, but a
2009/11/25 Elan Ruusamäe :
> On Wednesday 25 November 2009 11:36:38 Patryk Zawadzki wrote:
>> Switch to git / mercurial already? *hides*
> i'd see first git.pld-linux.org operating for the developer community first,
> but apparently nobody is working towards that.
It requires root access and I thi
On Wednesday 25 November 2009 11:36:38 Patryk Zawadzki wrote:
> Switch to git / mercurial already? *hides*
i'd see first git.pld-linux.org operating for the developer community first,
but apparently nobody is working towards that.
--
glen
___
pld-deve
2009/11/25 Elan Ruusamäe :
> http://www.cvsnt.org/manual/html/Substitution-modes.html
>
> here seems to be the doc to control the eol style.
>
> however i don't see a way to have mixed mode, so we should still go with
> approach of:
>
> 1. undos source
> 2. patch source with unix line endings.
>
>
On Sunday 21 June 2009 19:20:56 Elan Ruusamäe wrote:
> On Sunday 21 June 2009 19:11, hawk wrote:
> > - readded with -kb to keep CR/LF as required
>
> blah? undos the patched file(s) instead. reasons why are already discussed
> several times in this list.
http://www.cvsnt.org/manual/html/Substituti
Hi all!
I'm working on TeXLive2009 and when anybody follows the changes, can
see, that I'm splitting the texlive packages to a noarch and an
arch-depend part (texlive-texmf.spec and texlive.spec). The packages
names don't change (not will be e.g. texlive-texmf-latex-math or
similar, only texlive-l
14 matches
Mail list logo
