10:19 p.m.
Hello all,
Now that we've migrated to the new GitLab, I think it is time we revisit
the repositories we are still keeping (in archived form):
* aports.git and aports-old.git
Both are over 100 MB and both contain nothing helpful or useful to us
any more. They're snapshots of 2017 and 2018 Alpine packages, sometimes
with improvements that made it to system/ or user/. If we want to
investigate how Alpine did something we can just look in their current
Git instead of an old mirror. I'd like to remove both of these.
* portageplus.git
This is some patches to an old version of Portage, ca early 2017, that
supports emitting APK binpkgs. It also defaults to Galapagos instead of
Gentoo as a fallback repository. (How many here even remember Galapagos?)
We can probably archive the apkkit patch for posterity and then delete
it, IMO.
* patches.git
musl compatibility patches for some packages in /etc/portage/patches format.
My suggestion is take what we haven't packaged in packages.git and save
it somewhere (or maybe just package it?), then remove it.
* etc-portage.git, apkkit-conf.git, systemsite.git
Old infrastructure from when we were a Gentoo fork. Maybe archive for
posterity, or delete it.
Comments welcome.
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
10:22 p.m.
New subject: [adelie-devel] Removing old Git repositories from GitLab
Why?
100MB isn't a lot of space, I doubt it is particularly useful for us
anymore but I don't specifically see a benefit in deleting this past work;
esp. when it may involve products we still need to complete integrating
into Adele.
On Sun, Jul 14, 2019 at 9:20 PM A. Wilcox <awilfox(a)adelielinux.org> wrote:
Hello all,
Now that we've migrated to the new GitLab, I think it is time we revisit
the repositories we are still keeping (in archived form):
* aports.git and aports-old.git
Both are over 100 MB and both contain nothing helpful or useful to us
any more. They're snapshots of 2017 and 2018 Alpine packages, sometimes
with improvements that made it to system/ or user/. If we want to
investigate how Alpine did something we can just look in their current
Git instead of an old mirror. I'd like to remove both of these.
* portageplus.git
This is some patches to an old version of Portage, ca early 2017, that
supports emitting APK binpkgs. It also defaults to Galapagos instead of
Gentoo as a fallback repository. (How many here even remember Galapagos?)
We can probably archive the apkkit patch for posterity and then delete
it, IMO.
* patches.git
musl compatibility patches for some packages in /etc/portage/patches
format.
My suggestion is take what we haven't packaged in packages.git and save
it somewhere (or maybe just package it?), then remove it.
* etc-portage.git, apkkit-conf.git, systemsite.git
Old infrastructure from when we were a Gentoo fork. Maybe archive for
posterity, or delete it.
Comments welcome.
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
_______________________________________________
Ad?lie Development mailing list -- adelie-devel(a)lists.adelielinux.org
To unsubscribe send an email to adelie-devel-leave(a)lists.adelielinux.org
10:27 p.m.
New subject: [adelie-devel] Removing old Git repositories from GitLab
+1
I think the compatibility patches should be migrated if they're still
relevant, but other than that, it all can go.
On Sun, Jul 14, 2019 at 9:20 PM A. Wilcox <awilfox(a)adelielinux.org> wrote:
Hello all,
Now that we've migrated to the new GitLab, I think it is time we revisit
the repositories we are still keeping (in archived form):
* aports.git and aports-old.git
Both are over 100 MB and both contain nothing helpful or useful to us
any more. They're snapshots of 2017 and 2018 Alpine packages, sometimes
with improvements that made it to system/ or user/. If we want to
investigate how Alpine did something we can just look in their current
Git instead of an old mirror. I'd like to remove both of these.
* portageplus.git
This is some patches to an old version of Portage, ca early 2017, that
supports emitting APK binpkgs. It also defaults to Galapagos instead of
Gentoo as a fallback repository. (How many here even remember Galapagos?)
We can probably archive the apkkit patch for posterity and then delete
it, IMO.
* patches.git
musl compatibility patches for some packages in /etc/portage/patches
format.
My suggestion is take what we haven't packaged in packages.git and save
it somewhere (or maybe just package it?), then remove it.
* etc-portage.git, apkkit-conf.git, systemsite.git
Old infrastructure from when we were a Gentoo fork. Maybe archive for
posterity, or delete it.
Comments welcome.
--arw
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
_______________________________________________
Ad?lie Development mailing list -- adelie-devel(a)lists.adelielinux.org
To unsubscribe send an email to adelie-devel-leave(a)lists.adelielinux.org
7:43 a.m.
I'd say keep patches.git, drop the rest. But if there's any chance some
of the other repos might still be useful to anyone, it wouldn't cost us
anything to keep them all. 100MB isn't a lot of space, and since gitlab
displays archived repos on a separate tab, they don't even clutter our
repo list.
Cheers,
Luis
7:38 p.m.
New subject: [adelie-devel] Re: Removing old Git repositories from GitLab
On Jul 14 09:22 PM, Alyx Wolcott wrote:
On Sun, Jul 14, 2019 at 9:20 PM A. Wilcox
<awilfox(a)adelielinux.org> wrote:
> Hello all,
>
> Now that we've migrated to the new GitLab, I think it is time we revisit
> the repositories we are still keeping (in archived form):
>
> * aports.git and aports-old.git
>
> Both are over 100 MB and both contain nothing helpful or useful to us
> any more. They're snapshots of 2017 and 2018 Alpine packages, sometimes
> with improvements that made it to system/ or user/. If we want to
> investigate how Alpine did something we can just look in their current
> Git instead of an old mirror. I'd like to remove both of these.
If there are no unmerged changes these can probably be removed.
> * portageplus.git
>
> This is some patches to an old version of Portage, ca early 2017, that
> supports emitting APK binpkgs. It also defaults to Galapagos instead of
> Gentoo as a fallback repository. (How many here even remember Galapagos?)
>
> We can probably archive the apkkit patch for posterity and then delete
> it, IMO.
I say keep it for posterity.
> * patches.git
>
> musl compatibility patches for some packages in /etc/portage/patches
> format.
>
> My suggestion is take what we haven't packaged in packages.git and save
> it somewhere (or maybe just package it?), then remove it.
Sounds reasonable.
> * etc-portage.git, apkkit-conf.git, systemsite.git
>
> Old infrastructure from when we were a Gentoo fork. Maybe archive for
> posterity, or delete it.
Archive for posterity please.
Why?
100MB isn't a lot of space, I doubt it is particularly useful for us
anymore but I don't specifically see a benefit in deleting this past work;
esp. when it may involve products we still need to complete integrating
into Adele.
Agreed.
Max
665
days inactive
666
days old
adelie-project@lists.adelielinux.org
4 comments
5 participants
participants (5)
-
A. Wilcox -
Alyx Wolcott -
Kiyoshi Aman -
Luis Ressel -
Max Rees