Mailinglist Archive: zypp-devel (58 mails)
| < Previous | Next > |
Re: [zypp-devel] where to maintaining zypp pacakges
- From: Jiri Srain <jsrain@xxxxxxx>
- Date: Fri, 19 Jun 2009 15:37:00 +0200
- Message-id: <200906191537.01867.jsrain@xxxxxxx>
Dne pátek 19 Červen 2009 15:28:16 Michael Andres napsal(a):
Why?
YaST:Head is the devel project we submit to, and one needs to submit manually.
YaST:Svn is being submitted to automatically and thus contains more unstable
code.
YaST is a little bigger project than ZYPP and I don't think that the ZYPP
approach can work well (at least not as long as we submit directly to trunk).
Instead it can make sense to build YaST against zypp:Head?
Jiri
--
Regards,
Jiri Srain
YaST Team Leader
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: jsrain@xxxxxxx
Lihovarska 1060/12 tel: +420 284 028 959
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Friday 19 June 2009 13:25:45 Jano Kupec wrote:
Exactly. The problem is that in one point you can have a set of packages
that you want to submit to Factory, but in the next minute a change from
git master HEAD can appear there in some of the packages that you did
not want there.
Or is this not a problem? Don't we care what will go to Factory as long
as it passes the tests?
Well, we should not submitt to git:master, if our change isn't a candidate
for Factory. And if more than one package is affected, we usually talk to
each other.
One (not so big) problem i see with this is for example with versioning.
This way we will often submit packages having changes but without
increasing the version, or packages with changes made after the version
was increased.
This depends on how we maintain the version number when checking into
git:master. Actually there are several people using zypp::Head to test new
features (even on openSuSE-11.1). So we should try to maintain reasonable
version numbers.
Basically you are of course right. But as long as just we 4 are involved, I
don't feel urgent need. But let's wait until Duncan is back from vacation.
Maybe we can tune Hudson to feed zypp::Head with each commit and do
snapshots for zypp::Factory on demand. Maybe we find some (half) automated
solution, that also gives feedback to the git repo (e.g by tagging versions
scheduled and accepted for factory).
AFAIK it's no longer used. yast:svn used to build against this, but
that's probably history. So we could delete it.
Let's do it (we'll someone please do it, i don't have the rights IIRC).
Duncan? Stano? Coolo? (delete obs yast:svn)
Why?
YaST:Head is the devel project we submit to, and one needs to submit manually.
YaST:Svn is being submitted to automatically and thus contains more unstable
code.
YaST is a little bigger project than ZYPP and I don't think that the ZYPP
approach can work well (at least not as long as we submit directly to trunk).
Instead it can make sense to build YaST against zypp:Head?
Jiri
--
Regards,
Jiri Srain
YaST Team Leader
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: jsrain@xxxxxxx
Lihovarska 1060/12 tel: +420 284 028 959
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |