Mailinglist Archive: zypp-devel (58 mails)
| < Previous | Next > |
Re: [zypp-devel] where to maintaining zypp pacakges
- From: Michael Andres <ma@xxxxxxx>
- Date: Fri, 19 Jun 2009 15:28:16 +0200
- Message-id: <200906191528.16806.ma@xxxxxxx>
On Friday 19 June 2009 13:25:45 Jano Kupec wrote:
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.
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).
Duncan? Stano? Coolo? (delete obs yast:svn)
--
cu,
Michael Andres
+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres YaST Development ma@xxxxxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0
+------------------------------------------------------------------+
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
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)
--
cu,
Michael Andres
+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres YaST Development ma@xxxxxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0
+------------------------------------------------------------------+
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |