| 1 |
On Tuesday 12 October 2004 23:00, ashish gawarikar wrote: |
| 2 |
|
| 3 |
> The advantage of doing this is viz: |
| 4 |
> |
| 5 |
> 1. QA has to test one huge download and dont have to test different |
| 6 |
> scenarios. |
| 7 |
|
| 8 |
Downloading itself is hardly an issue. Believe me, we do enough support. |
| 9 |
|
| 10 |
|
| 11 |
> 2. You exactly know what packages you are getting in this download |
| 12 |
|
| 13 |
You can pin a dependency to a specific version. Say you have a meta-ebuild |
| 14 |
mycompanysetup-1.0.1.ebuild and you pin it to depend on very specific |
| 15 |
versions of other ebuilds (up to the revision number). |
| 16 |
|
| 17 |
> 3. You have to issue one-and-only-one command for upgrade |
| 18 |
|
| 19 |
Updating this meta-ebuild will automatically update all dependencies as |
| 20 |
you have pinned down the versions you want. Note that ebuilds themselves |
| 21 |
(the build descriptions) are downloaded all together by rsync, or in case |
| 22 |
of a local overlay the way you decide to distribute it (CVS, subversion?, |
| 23 |
rsync). The source tarballs are checksummed and veryfied before use. |
| 24 |
Except the theoretical posibility of malice there is not much that can go |
| 25 |
wrong here. Just put the tarballs on a webserver and it works. |
| 26 |
|
| 27 |
Paul |
| 28 |
|
| 29 |
-- |
| 30 |
Paul de Vrieze |
| 31 |
Gentoo Developer |
| 32 |
Mail: pauldv@g.o |
| 33 |
Homepage: http://www.devrieze.net |
Archives