| 1 |
On 10/29/2014 7:37 AM, Martin Vaeth <martin@×××××.de> wrote: |
| 2 |
> The long-term plans are to drop PORTDIR and PORTDIR_OVERLAY |
| 3 |
> completely, the reason being that it is not flexible enough: |
| 4 |
> With repos.conf you can specify details for every repository, |
| 5 |
> you are not even forced to have a *single* major repository |
| 6 |
> (AFAIK, this is called mix-ins in some other package managers), |
| 7 |
> etc. |
| 8 |
|
| 9 |
Ok, thanks Martin/guys... |
| 10 |
|
| 11 |
So, the short answer is: |
| 12 |
|
| 13 |
"Don't worry about it, if/when something needs to be done to prevent |
| 14 |
breakage, we will let you know ahead of time via a news item or other |
| 15 |
appropriate method." |
| 16 |
|
| 17 |
Which sounds like the right thing to do for those of us who prefer |
| 18 |
stability to (too much) bleeding edge? |
| 19 |
|
| 20 |
But - for those of us who, while preferring stability, also might like |
| 21 |
to get a jump on things *if* switching to repos.conf now is: |
| 22 |
|
| 23 |
a) easy, |
| 24 |
b) fully supported, and |
| 25 |
c) considered perfectly stable, |
| 26 |
|
| 27 |
would it be possible for someone with intimate knowledge of the details |
| 28 |
to write up a wiki page for how to go about it? |
| 29 |
|
| 30 |
Thanks again! |
Archives