| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Barry Shaw wrote: |
| 5 |
|
| 6 |
| I guess what I'm describing isn't strictly an enterprise gentoo (which I |
| 7 |
| don't think the community has the resources to support), more of a |
| 8 |
| slowed down version of the main portage tree. In my experience |
| 9 |
| maintaining a couple of hundred of gentoo machines centrally, its the |
| 10 |
| rapid pace of change in the main tree that causes problems. We only |
| 11 |
| only upgrade packages for security reasons, but whenever we do this, we |
| 12 |
| are forced to upgrade a multitude of other packages because they've |
| 13 |
| dropped out of portage. If we only had to upgrade packages for security |
| 14 |
| and depreciation reasons it would make for a much more stable |
| 15 |
| environment for the end users (which is what we're after ultimately) and |
| 16 |
| ~ it would make maintenence more manageable. |
| 17 |
I like this idea. It fits better with the way Gentoo already runs, and will |
| 18 |
work nicely once the pending glsa/emerge integration is complete. Another |
| 19 |
thought on top of this is that it would make sense to throw out the idea of |
| 20 |
enterprise snapshots alltogether. Instead, on the local system never force a |
| 21 |
user to install a new version if their current version's ebuild is removed from |
| 22 |
portage. So basicly, use the ebuilds that are already cached as a portage |
| 23 |
overly. This also has a second benifit on the unstable side. If someone needs |
| 24 |
to install an unstable package but that ebuild is later dropped in favor of a |
| 25 |
newer unstable version currently on the next emerge sync; emerge -Up world; the |
| 26 |
unstable package will be uninstalled and replaced by the current stable version |
| 27 |
(unless the issue is first addressed before the update). This can be |
| 28 |
troublesom, especially if someone is to quick and didn't notice that the |
| 29 |
package is being downgraded. |
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 34 |
|
| 35 |
iD8DBQFA/d61iP+LossGzjARAkrpAJ0bHE9JV56ttk6dL3FM1XVS6LoMcACePNbH |
| 36 |
gro06Mifc/j9csS6KMuzlBI= |
| 37 |
=0+81 |
| 38 |
-----END PGP SIGNATURE----- |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives