Re: SPECS: template-python.spec - python 2.4 is only in AC line, let's use (kin...

2009-01-23 Thread wrobell 
On Fri, Jan 23, 2009 at 12:52:40PM +0200, Elan Ruusamäe wrote:
> On Friday 23 January 2009 02:30:52 wrobell wrote:
> > but i do care. i really want to know why i am supposed to maintain some
> > support for obsolete software on HEAD.  my only conclusion is - AC line.
> what support? you don't have to _add_ anything, it it's present, leave it, 
> don't touch it?

for example, please take a look at commit fight around mx.DateTime in
python-psycopg2.spec. the ones, who constantly were reverting my changes
never bothered to contact me or to respond why they are doing that.

so, please, respect my time, ok?

[...]

regards,

wrobell 
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: New names for commons and struts spec files

2009-01-23 Thread Adam Golebiowski 
On Friday 23 January 2009, Paweł Zuzelski wrote:
> cvsadmin, please copy following files in SPECS:
>
> jakarta-commons-codec  -> java-commons-codec
> jakarta-commons-discovery  -> java-commons-discovery
> jakarta-commons-httpclient -> java-commons-httpclient
> jakarta-commons-lang   -> java-commons-lang
> jakarta-commons-net-> java-commons-net
> jakarta-commons-validator  -> java-commons-validator
> jakarta-struts -> java-struts
>
> commons and struts are no longer subprojects of jakarta.

Cp-ed, please do a cvs rm on jakarta-*.spec.

For future reference, in order to ease cvsadmins work and avoid potential 
mistakes please provide such requests in ready to paste format:

cp $old_spec,v $new_spec,v

as in:

cp jakarta-commons-codec.spec,v java-commons-codec.spec,v

thanks.

adamg,v

-- 
 http://www.mysza.eu.org/ | Everybody needs someone sure, someone true,
   PLD Linux developer| Everybody needs some solid rock, I know I do.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

New names for commons and struts spec files

2009-01-23 Thread Paweł Zuzelski 
cvsadmin, please copy following files in SPECS:

jakarta-commons-codec  -> java-commons-codec
jakarta-commons-discovery  -> java-commons-discovery
jakarta-commons-httpclient -> java-commons-httpclient
jakarta-commons-lang   -> java-commons-lang
jakarta-commons-net-> java-commons-net
jakarta-commons-validator  -> java-commons-validator
jakarta-struts -> java-struts

commons and struts are no longer subprojects of jakarta.

-- 
.Pozdrawiam, .
  .  Pawel Zuzelski.
. jid:p...@touk.pl.
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Re: SPECS: template-python.spec - python 2.4 is only in AC line, let's use (kin...

2009-01-23 Thread Elan Ruusamäe 
On Friday 23 January 2009 02:30:52 wrobell wrote:
> but i do care. i really want to know why i am supposed to maintain some
> support for obsolete software on HEAD.  my only conclusion is - AC line.
what support? you don't have to _add_ anything, it it's present, leave it, 
don't touch it?

> anyway, AC-branch is better solution. there would be no problem, then.

why fighting with windmill?

this is totally __IRRELEVANT__ is the cond %{pld_release} or %{py_ver} 
comparision, the condition is still there. and both are easily grappable (for 
whatever reason you need to _find_ these).

my +1 for %{py_ver} cmp, as that's what it really is (py_ver not dist_line)

py2.5 to ac line is unlikely to happen officially, but you are still allowed 
to do such port on your own, for those people you would be chopping off their 
feet.

-- 
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en