3
5
Fork
You've already forked xut
3

How to contribute to origin repo #8

Closed
opened 2025年10月07日 13:32:54 +02:00 by zenobit · 3 comments
Contributor
Copy link

Now xut works in merged repository which is nice
But how to handle updating templates in their origin repo?

eq: I will update in merged repo some template from abyss
I want to push changes also to abyss to make PR to your origin repo (or hyprland etc..)

Now xut works in merged repository which is nice But how to handle updating templates in their origin repo? eq: I will update in merged repo some template from abyss I want to push changes also to abyss to make PR to your origin repo (or hyprland etc..)

I am not sure what is the problem. The repos are synced and the merged dir is created in every run - maybe there is a bug there? Can you be more specific please?

I am not sure what is the problem. The repos are synced and the merged dir is created in every run - maybe there is a bug there? Can you be more specific please?
Author
Contributor
Copy link

i am working in ./xut/_void-linux_void-packages repo

update some templates which older version is in abyss-packages

looking for easier way to copy updated template dir to "source" repo for creating MR there

xut could handle:
delete old template dir in abyss (maybe i deleted some no longer needed patch) and then copy updated dir with templates/patches to abyss (or any other xtra repo)

for that we need to track where is origin of template
void, abyss or another extra repo

i am working in ./xut/_void-linux_void-packages repo update some templates which older version is in abyss-packages looking for easier way to copy updated template dir to "source" repo for creating MR there xut could handle: delete old template dir in abyss (maybe i deleted some no longer needed patch) and then copy updated dir with templates/patches to abyss (or any other xtra repo) for that we need to track where is origin of template void, abyss or another extra repo

xut is meant to use third-party template repos.
If you try to add the functionality you describe it can easily blow up in size and complexity. I do not want that.
Having said that, reusing the directory structure, cloned repos, even xutconf and some functions from xut makes perfect sense for a companion script 👍
xutup maybe? 😛

xut is meant to use third-party template repos. If you try to add the functionality you describe it can easily blow up in size and complexity. I do not want that. Having said that, reusing the directory structure, cloned repos, even xutconf and some functions from xut makes perfect sense for a companion script 👍 xutup maybe? 😛
Sign in to join this conversation.
No Branch/Tag specified
master
template_list_cache
find_repodir_caching
unique_repodir_names
mobinmob-patch-1
yet_another_touch
mdocs
moar_fixes
seperate_build_preparation
root_check
ls_to_list_dirs
CONF_WORKDIR.override
safety_portability_fixes
fix_updates
fixes_and_find
get_key_from_template
v.0.3
v.0.2
dev
manyrepos
v.0.4.2
0.4.1
v.0.3.1
v.0.3
v.0.2.1
v.0.2
v.0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mobinmob/xut#8
Reference in a new issue
mobinmob/xut
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?