| 1 |
> The purpose of overlays is to have ebuilds maintained outside of the |
| 2 |
> official Gentoo portage. Importing a ebuild from an overlay whether it |
| 3 |
> uses Git or not means importing the ebuild(s). In the Git context, it |
| 4 |
> means the Gentoo maintainer has to make an import commit the same way |
| 5 |
> it would be done to start a project with somthing like: |
| 6 |
> |
| 7 |
> cp 'files to be commited' . |
| 8 |
> git add . |
| 9 |
> git commit -m 'initial import' |
| 10 |
> |
| 11 |
> So, like explained before your concern is clearly out of the current |
| 12 |
> discussion. Importing commit history from Overlays is not supported and |
| 13 |
> will probably never be. |
| 14 |
|
| 15 |
Which does not mean that it's not desirable. |
| 16 |
|
| 17 |
The KDE ebuilds are mainly evolving inside the KDE overlay, where KDE betas |
| 18 |
and live ebuilds live. Being able (in the future) to see the history of an |
| 19 |
ebuild before it was imported into the main tree would certainly help in some |
| 20 |
cases. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Andreas K. Huettel |
| 25 |
Gentoo Linux developer |
| 26 |
kde, sci, arm, tex, printing |
Archives