From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 24 Apr 2009 21:43:58 +0400 From: Alexey Tourbin To: ALT Linux Team development discussions Message-ID: <20090424174358.GN9391@altlinux.org> Mail-Followup-To: ALT Linux Team development discussions Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hR5hZbB3sAoKVpMi" Content-Disposition: inline Subject: [devel] collaboration patterns (was: FAILED fpc.git=2.2.4-alt1) X-BeenThere: devel@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ALT Linux Team development discussions List-Id: ALT Linux Team development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2009 17:43:59 -0000 Archived-At: List-Archive: List-Post: --hR5hZbB3sAoKVpMi Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 24, 2009 at 08:01:39PM +0300, Slava Dubrovskiy wrote: > >>> Why? Just rebuild that another package with new fpc. > >>> =20 > >> =FE=D4=CF=C2=D9 =DC=D4=CF=D4 =C4=D2=D5=C7=CF=CA =D0=C1=CB=C5=D4 =D0=C5= =D2=C5=D3=CF=C2=D2=C1=D4=D8 =D3 =CE=CF=D7=D9=CD fpc, =CE=D5=D6=CE=CF =DE=D4= =CF=C2=D9 =CF=CE (=CE=CF=D7=D9=CA > >> fpc) =D0=CF=D0=C1=CC =D7 =D2=C5=D0=CF=DA=C9=D4=C1=D2=C9=CA. =E1 =CF=CE= =CE=C5 =CD=CF=D6=C5=D4, =D4.=CB. =C1=CE=CD=C5=D4=D9 =CE=C5 =D0=D5=D3=CB=C1= =C0=D4. > >> =FA=C1=CD=CB=CE=D5=D4=D9=CA =CB=D2=D5=C7. > >> =F1 =D4=C1=CB =D0=CF=CE=C9=CD=C1=C0 =CE=D5=D6=CE=CF =C9=CC=C9 =D3=CF= =C2=C9=D2=C1=D4=D8 =D7=D3=C5 =CF=C4=CE=CF=D7=D2=C5=CD=C5=CE=CE=CF, =C9=CC= =C9 =C4=C5=CC=C1=D4=D8 =C4=D7=C5 =D7=C5=D2=D3=C9=C9 > >> fpc. > >> =20 > > Yes, you have to add that another package to your fpc task. > > If you have ACL permissions to build that another package, > > this is remarkably simple. :) And if you don't, this is still > > possible. > > =20 > =E4=C1, =CE=C1=D7=C5=D2=CE=CF =D3=C5=CA=DE=C1=D3, =CB=CF=C7=C4=C1 =D4=C1= =CB=CF=CA =D0=C1=CB=C5=D4 =D7=D3=C5=C7=CF =CF=C4=C9=CE, =DC=D4=CF =C2=D5=C4= =C5=D4 =D0=D2=CF=D3=D4=CF. =E1 > =C5=D3=CC=C9 =DA=C1=D7=D4=D2=C1 =C9=C8 =C2=D5=C4=C5=D4 =C2=CF=CC=D8=DB=C5= =CF=C4=CE=CF=C7=CF? =E1 =CB=C1=D6=C4=D9=CA =CD=C1=CE=D4=C5=CA=CE=C5=D2 =CC= =C9=DE=CE=CF=D3=D4=D8 =C9 =CB > =CB=C1=D6=C4=CF=CD=D5 =CE=C1=CA=D4=C9 =D0=CF=C4=C8=CF=C4... Okay, let's discuss again what I call "collaboration patterns". The problem is that we need to find the right balance between two things: 1) the maintainer must be responsible for the package, and thus she should be able to control other the package; 2) sometimes, when it comes to the repo, there should be other ways to make minor changes to the package, perhaps even without the maintainer. I see the following possibilities: 1) For fpc packages and packages which have fpc parts, you may ask for permanent ACL permissions as a co-maintainer. There might be an informal agreement between you and maintainer so that you can make fpc-related changes without prior notice (and otherwise discuss any changes first). 2a) You can ask her for single NMU ACK. 2b) You can ask girar administrator for single NMU ACK. 3) You can share your fpc task and ask her to push new package into your shared fpc task. Are there any better possibilities? I believe we need to make rebuilding packages for new dependencies easily possible. And otherwise we face major problems. > > Please don't do the second fpc package. > =EB=CF=CE=C5=DE=CE=CF =CE=C5 =C2=D5=C4=D5. Now, what is the problem with two fpc packages, e.g. fpc1 and fpc2? Consider there are two external fpc modules, foo-fpc and bar-fpc. It is then possible that foo-fpc was build with fpc1, while bar-fpc was built with fpc2. So what? There are no unmet dependencies, but you cannot use both fpc-foo and fpc-bar for in a single program. --hR5hZbB3sAoKVpMi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknx+l4ACgkQfBKgtDjnu0YpVACeLV9W7uRuBVTgG5dbfl/1Pgex P7wAnj75Hyum2sTFiare26oHBFz2+vZv =gqWU -----END PGP SIGNATURE----- --hR5hZbB3sAoKVpMi--