| 1 |
On Donnerstag 11 Februar 2010, Mark Knecht wrote: |
| 2 |
> On Thu, Feb 11, 2010 at 12:49 PM, Alan McKinnon <alan.mckinnon@×××××.com> |
| 3 |
wrote: |
| 4 |
> > On Thursday 11 February 2010 22:37:00 Mark Knecht wrote: |
| 5 |
> >> On Thu, Feb 11, 2010 at 12:24 PM, Alan McKinnon |
| 6 |
> >> <alan.mckinnon@×××××.com> |
| 7 |
> > |
| 8 |
> > wrote: |
| 9 |
> >> > On Thursday 11 February 2010 22:09:28 Mark Knecht wrote: |
| 10 |
> >> >> Can someone comment on why I do or do not want to include config |
| 11 |
> >> >> files when making quickpkg files? |
| 12 |
> >> >> |
| 13 |
> >> >> Seems like there is the issue of hand edits being saved which would |
| 14 |
> >> >> be a good reason to keep them. I'm not overly worried about someone |
| 15 |
> >> >> stealing them and getting access to settings, but I can see that |
| 16 |
> >> >> might be a good reason not to. |
| 17 |
> >> >> |
| 18 |
> >> >> If I don't save them and then after a crash want to use binary |
| 19 |
> >> >> packages to get a machine running quickly it seems like I'd want to |
| 20 |
> >> >> include everything I could. |
| 21 |
> >> >> |
| 22 |
> >> >> What would the more experienced user do for the single-user desktop |
| 23 |
> >> >> type user? |
| 24 |
> >> > |
| 25 |
> >> > The config of the package you quickpkg'ed likely works. |
| 26 |
> >> > emerge -k is most often used to revert your own mistakes, so you want |
| 27 |
> >> > the thing to work. Your latest configs are suspect, why insist they |
| 28 |
> >> > take priority? You can always rename them to <name>.bak if you think |
| 29 |
> >> > they might get nuked. |
| 30 |
> >> > |
| 31 |
> >> > Why do you care if someone steals your quickpkgs? Put them in a |
| 32 |
> >> > directory owned by root, they are then as safe as your stuff in /etc. |
| 33 |
> >> > To get to the tarballs, they must get to a place where they can just |
| 34 |
> >> > read the originals.... |
| 35 |
> >> |
| 36 |
> >> Thanks Alan. That confirms what I was thinking. |
| 37 |
> >> |
| 38 |
> >> My comment about things getting stolen is that I might burn them to |
| 39 |
> >> DVD for safe keeping in which case anyone can walk off with the DVD. |
| 40 |
> >> I'm not overly worried about that and it's far and away less of an |
| 41 |
> >> issue than getting the machine back to a running state. |
| 42 |
> > |
| 43 |
> > OK, I see. |
| 44 |
> > |
| 45 |
> > As long as you know which configs have password in them and take |
| 46 |
> > precautions, you should be OK. |
| 47 |
> > |
| 48 |
> > For the truly paranoid (and there will be someone who is validly so) |
| 49 |
> > another option is to store /etc in a remote SVN instance that is |
| 50 |
> > secured, and not store configs with the quickpkgs |
| 51 |
> |
| 52 |
> Thanks. Like I said originally I'm not worried about it but at least |
| 53 |
> you understood why I asked. |
| 54 |
> |
| 55 |
> One thing I haven't found so far is what to put in make.conf to get |
| 56 |
> the buildpkg feature to include the configs. It's easy at the command |
| 57 |
> line. Where's the documentation on how to actually use this the right |
| 58 |
> way automatically? |
| 59 |
> |
| 60 |
> - Mark |
| 61 |
|
| 62 |
when you use buildpkg feature the packages contain the virgin unedited configs |
| 63 |
as they are installed by the package and not any edits done by you. |
Archives