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