ALHP for arch testing repos? #58
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#58
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there a possibility for there to be builds of the testing repos as well? For instance there being a
testing-x86-64-v3
andcommunity-testing-x86-64-v3
? Or will ALHP just be restricted to only the stable repos?I think @anonfunc doesn't build the testing pacakge because it will be too many package to rebuild again and again with some reiterations, since the build system see if there any changes in the svn2git, for example, if a package as a reiterations again 1 hours after it, and that multiple pacakges do it, you will rapibly see many pacakges being in queue again and again.
I don't know if it is the official reason, but that my though about it
There is no technical reason to not build
testing
, but I see no practical reason to build it.testing
, as the name suggests, provides a opportunity to tests if package X works as expected and works with the rest of Archlinux's software env., which is not our (direct) concern.As the ALHP repos only 'replace' the Archlinux official (non-testing-)version you could have testing enabled even with ALHP-repos active (testing>ALHP>non-testing).
Hm ok. I've just always had the testing repos enabled lol.