| 1 |
On Thursday 25 of November 2010 16:07:45 Alexis Ballier wrote: |
| 2 |
> On Thursday 25 November 2010 11:22:39 Paweł Hajdan, Jr. wrote: |
| 3 |
> > On 11/25/10 2:59 PM, Alexis Ballier wrote: |
| 4 |
> > > I fail to understand why you claim that live ebuilds are a QA |
| 5 |
> > > nightmare, you may want to have a look at how I play with, eg, ffmpeg |
| 6 |
> > > or vlc and their live ebuilds: they make version bumps much easier and |
| 7 |
> > > far less error prone. |
| 8 |
> > |
| 9 |
> > I'm just curious. Could you explain more how the live ebuilds make |
| 10 |
> > version bumps easier and less error prone? |
| 11 |
> |
| 12 |
> By following closely upstream development you are able to adapt the live |
| 13 |
> ebuild to the current status, eg, for new deps. Usually with vlc, when a |
| 14 |
> new major version comes out, there are a couple of new features and a |
| 15 |
> couple of outdated features removed, doing all these changes at once is |
| 16 |
> more error prone than doing it once you notice the change for each of them |
| 17 |
> in the live ebuild. |
| 18 |
> |
| 19 |
> As for version bumps, the live ebuild is simply copied to an ebuild with a |
| 20 |
> name matching the version that has just been released. |
| 21 |
|
| 22 |
It may be worth mentioning it's exactly how all kde-base ebuilds are prepared. |
| 23 |
We just svn up in distfiles occasionally, look for changes in buildsystem and |
| 24 |
adjust live (stable branch or trunk) ebuilds accordingly (that being said |
| 25 |
4.x.9999 live ebuilds usually reflect the best KDE version available). |
| 26 |
Many Gentoo KDE devs use 4.x.9999 on daily basis (and actually they should) |
| 27 |
and thus are able to evaluate patches and take them directly from disfiles via |
| 28 |
svn diff -r prev:patchrev to tree if needed. |
| 29 |
Ebuilds you see in tree are just generated versions of live ones (blind copy |
| 30 |
with replaced keywords, we use bump tool for it however). |
| 31 |
|
| 32 |
-- |
| 33 |
regards |
| 34 |
MM |
Archives