What approach to evaluate edition? #152
Labels
No labels
Done
bug
buildiso
buildpkg
buildtree
critical
deployiso
duplicate
enhancement
help wanted
in progress
invalid
manjaro-chroot
note
old-not-relevant
optional
question
sonar
todo
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#152
Loading…
Add table
Add a link
Reference in a new issue
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?
Created by: udeved
We got basically two possible takes on evaluating the edition type.
a) tie it to a buildset
disadvantage: we can't really distinguish eg sonar with that, since they have gnome/mate "community overlay"
b) have a profile based var edition_type
disadvantage: we would have to run deployiso in the profile dir, which wouldn't matter if buildiso ran deployiso after build
I changed from a) to b).
edition_type would also represent the upload category.
Any thoughts or different approach?
Created by: udeved
Do we want $arch subdirs per iso edition?