| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi Ben, |
| 5 |
|
| 6 |
On Tue, August 24, 2004 9:54 pm, Ben Munat said: |
| 7 |
> Anyone have any idea why my emerge -p is showing: |
| 8 |
> |
| 9 |
> [ebuild N ] www-apps/gallery-1.4.4-r1 |
| 10 |
> |
| 11 |
|
| 12 |
This is because the new gallery uses webapp-config and all the |
| 13 |
webapp-config aware ebuilds are SLOTted on ${PVR} this is so that if you |
| 14 |
have the new vhosts use flag enabled you can have multiple versions of a |
| 15 |
webapp installed in different locations. |
| 16 |
|
| 17 |
> when I already have (and am using) gallery? If portage thinks it will be |
| 18 |
> a new install, is it likely to trash my configuration? |
| 19 |
> |
| 20 |
|
| 21 |
When you run the install if you have vhosts use flag enabled then the |
| 22 |
webapp will only be merged to the system under /usr/share/webapps and you |
| 23 |
will need to use webapp-config to install gallery. If you don't have |
| 24 |
vhosts use flag enabled then webapp-config will be run automatically |
| 25 |
during the emerge of gallery and should upgrade the inplace gallery. |
| 26 |
|
| 27 |
I think that upgrading shouldn't trash you config files but I would |
| 28 |
recommend that a backup would always be a good idea before you upgrade ;) |
| 29 |
|
| 30 |
webapp-config will try and protect configuration files that have been |
| 31 |
identified by the ebuild writer and uses the etc-update mechanism to allow |
| 32 |
you to update them: |
| 33 |
|
| 34 |
from man webapp.eclass: |
| 35 |
- ---- |
| 36 |
Overwriting Configuration Files |
| 37 |
When packages are upgraded, new configuration files are installed. |
| 38 |
Different package managers handle |
| 39 |
this in different ways. Portage can prevent files being |
| 40 |
overwritten on a per-directory basis. |
| 41 |
Web-based applications normally have configuration files installed in |
| 42 |
the same directories as the |
| 43 |
scripts themselves. Packages for Portage, therefore, normally end |
| 44 |
up overwriting the configuration |
| 45 |
file because the alternative is having to wade through pages of |
| 46 |
etc-update output. |
| 47 |
|
| 48 |
webapp.eclass avoids this problem by allowing ebuilds to indicate |
| 49 |
which files are configuration |
| 50 |
files. webapp-config uses this information to ensure that |
| 51 |
configuration files are not overwritten. |
| 52 |
The administrator can then use etc-update as normal to complete the |
| 53 |
upgrade. |
| 54 |
- ---- |
| 55 |
|
| 56 |
Hope this info helps. |
| 57 |
|
| 58 |
Cheers |
| 59 |
- -- |
| 60 |
Peter |
| 61 |
|
| 62 |
-----BEGIN PGP SIGNATURE----- |
| 63 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 64 |
|
| 65 |
iD8DBQFBLCtHVPRdzag0AcURAk1TAJ9KRb3OgIKWr+RhX2M+/beeU1/LzQCaAoHu |
| 66 |
4XBqReB4ohykMz65aPH6ob0= |
| 67 |
=7Heo |
| 68 |
-----END PGP SIGNATURE----- |
Archives