Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-introduce Haiku Repository #143

Open
andponlin opened this issue Dec 20, 2017 · 2 comments
Open

Re-introduce Haiku Repository #143

andponlin opened this issue Dec 20, 2017 · 2 comments

Comments

@andponlin
Copy link
Collaborator

andponlin commented Dec 20, 2017

A while ago, the Haiku repository was removed because it just endlessly added new revisions of the main packages and they piled-up in the database. However Humdinger points out;

But then we won't have nice titles for the packages and no
translations. The user may look for the user guide in his language.

The haiku repo contains the following packages at the time of writing;

haiku_devel : r1...alpha4_pm_hrev51700.1 : X86_GCC2
haiku_loader : r1...alpha4_pm_hrev51700.1 : X86_GCC2
haiku : r1...alpha4_pm_hrev51700.1 : X86_GCC2
haiku_userguide_ca : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_de : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_en : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_es : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_fi : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_fr : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_hu : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_it : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_jp : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_pl : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_pt_br : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_pt_pt : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_ru : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_sk : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_sv_se : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_uk : r1...alpha4_pm_hrev51700.1 : ANY
haiku_userguide_zh_cn : r1...alpha4_pm_hrev51700.1 : ANY
haiku_welcome : r1...alpha4_pm_hrev51700.1 : ANY
haiku_x86_devel : r1...alpha4_pm_hrev51700.1 : X86_GCC2
haiku_x86 : r1...alpha4_pm_hrev51700.1 : X86_GCC2
makefile_engine : r1...alpha4_pm_hrev51700.1 : ANY
netfs : r1...alpha4_pm_hrev51700.1 : X86_GCC2
userland_fs : r1...alpha4_pm_hrev51700.1 : X86_GCC2
webpositive_x86 : r1...alpha4_pm_hrev51700.1 : X86_GCC2

A solution would be to have the option of marking certain repositories as "not keeping history" so older versions are deleted each time a new version arrives. Without this the versions will just pile-up with new versions.

Also a 'blacklist' might be helpful so that system-level packages are not tracked.

@humdingerb
Copy link
Collaborator

I was just thinking... Doesn't HDS only have to track the "official" Haiku repo once Beta is out, i.e. not the nightly version that adds a new revision für every commit?
Maybe we can re-add the "Haiku" repo with the release of Beta1 and won't have an overspilling history at all.

@andponlin
Copy link
Collaborator Author

Hi Humdinger. I don't think there is any plan anybody has communicated. I guess that would make sense. Let's leave this ticket open for now and try to remember once there is a repository up and running for the new beta. If there is one already I can hook HDS into that no problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants