| 1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
| 2 |
> On Thu, Feb 11, 2010 at 4:29 PM, Volker Armin Hemmann |
| 3 |
> <volkerarmin@××××××××××.com> wrote: |
| 4 |
> |
| 5 |
>> On Freitag 12 Februar 2010, Dale wrote: |
| 6 |
>> |
| 7 |
> <SNIP> |
| 8 |
> |
| 9 |
>>> This is how I understand it. If you use buildpkg with emerge, you get |
| 10 |
>>> the original configs from the source tarball. If you use quickpkg, then |
| 11 |
>>> you get the config files YOU created. If I understand this correctly, |
| 12 |
>>> you can remember it this way as well. Doing it during the emerge gives |
| 13 |
>>> you what emerge produces. Doing it with quickpkg gives you what you |
| 14 |
>>> produced. |
| 15 |
>>> |
| 16 |
>>> All that and I didn't confuse myself. So, I'm probably wrong in how I |
| 17 |
>>> understand it. lol |
| 18 |
>>> |
| 19 |
>>> Dale |
| 20 |
>>> |
| 21 |
>>> :-) :-) |
| 22 |
>>> |
| 23 |
>> no, this is entirely correct. |
| 24 |
>> |
| 25 |
>> |
| 26 |
>> |
| 27 |
> > From what I've seen last night and today I do not think this is correct. |
| 28 |
> |
| 29 |
> quickpkg =NAME |
| 30 |
> |
| 31 |
> produces a binary package with NO config files included. |
| 32 |
> |
| 33 |
> You have to use |
| 34 |
> |
| 35 |
> quickpkg --include-configs =NAME |
| 36 |
> |
| 37 |
> to get the configs, at least from what I can see from the messages it |
| 38 |
> produces when it runs. |
| 39 |
> |
| 40 |
> There is another option to limit the configs to only the unedited ones. |
| 41 |
> |
| 42 |
> - Mark |
| 43 |
> |
| 44 |
> |
| 45 |
|
| 46 |
You do have to add that option but that was already mentioned. I should |
| 47 |
have added it for clarity tho. |
| 48 |
|
| 49 |
Dale |
| 50 |
|
| 51 |
:-) :-) |
Archives