| 1 |
On Freitag 12 Februar 2010, Mark Knecht wrote: |
| 2 |
> On Thu, Feb 11, 2010 at 2:33 PM, Alan McKinnon <alan.mckinnon@×××××.com> |
| 3 |
wrote: |
| 4 |
> > On Friday 12 February 2010 00:13:23 Volker Armin Hemmann wrote: |
| 5 |
> >> > One thing I haven't found so far is what to put in make.conf to get |
| 6 |
> >> > the buildpkg feature to include the configs. It's easy at the command |
| 7 |
> >> > line. Where's the documentation on how to actually use this the right |
| 8 |
> >> > way automatically? |
| 9 |
> >> > |
| 10 |
> >> > |
| 11 |
> >> > |
| 12 |
> >> > - Mark |
| 13 |
> >> |
| 14 |
> >> when you use buildpkg feature the packages contain the virgin unedited |
| 15 |
> >> configs as they are installed by the package and not any edits done by |
| 16 |
> >> you. |
| 17 |
> > |
| 18 |
> > Just checking something: |
| 19 |
> > |
| 20 |
> > We are all aware of the difference between |
| 21 |
> > |
| 22 |
> > emerge --buildpkg |
| 23 |
> > |
| 24 |
> > and |
| 25 |
> > |
| 26 |
> > quickpkg |
| 27 |
> > |
| 28 |
> > right/ |
| 29 |
> > |
| 30 |
> > -- |
| 31 |
> > alan dot mckinnon at gmail dot com |
| 32 |
> |
| 33 |
> Volker is. I am not sure I am and I'm not sure that Neil was talking |
| 34 |
> about quickpkg which is what I am using so far. The command |
| 35 |
> |
| 36 |
> quickpkg --include-configs |
| 37 |
> |
| 38 |
> says it includes the configs. That's what I thought we (you and I |
| 39 |
> Alan) were talking about. |
| 40 |
> |
| 41 |
> On the other hand I presumed (apparently incorrectly) that the |
| 42 |
> FEATURES="buildpkg" (which is what I think Neil is speaking about) |
| 43 |
> gave me the same option but I now guess it doesn't. |
| 44 |
> |
| 45 |
> If I need to use quickpkg to save the configs then I think I'll do |
| 46 |
> that being that as I simple-minded home user with no admin experience |
| 47 |
> I have no in-place rigorous methods for doing __any__ backups. I just |
| 48 |
> tar up directories once in awhile and deal with the problems that come |
| 49 |
> later. (If they come...when they come...they do come, don't they?) ;-) |
| 50 |
> |
| 51 |
> - Mark |
| 52 |
|
| 53 |
when you use quickpkg it package up all the files belonging to the package as |
| 54 |
they are installed in your system. If you edited the configs (or any other file) |
| 55 |
the edited version ends in the tarball. |
| 56 |
|
| 57 |
with buildpkg the package is created before the files are copied into the |
| 58 |
filesystem. Config files included in the tarball are 'virgin'. |
| 59 |
|
| 60 |
buildpkg is 'cleaner' because you get everything as it is installed. If you |
| 61 |
want to save your configs - well, regular backups of /etc is always a smart |
| 62 |
choice. |
Archives