option to create torrent #238
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#238
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
move torrent creation from deployiso to buildiso
Created by: philmmanjaro
Does this make sense to do so? I thought http seed should be part of our torrents. How should that buildiso know?
Created by: udeved
Well, from code pov, it would make sense.
I removed torrent from deployiso, because it duplicates code.
Since rsync syncs directories, the initsys and arch is only relevant to iso file name.
But rsync doesn't care for filenames.
So it would be better, if torrents could be created after build process.
Its perhaps also in Strits's interest, he would get the torrent files that deployiso uploads?
Created by: udeved
Oh. its easy to make buildiso know the webseed url from manjaro-tools.conf ;)
Created by: udeved
The last commit makes deployiso generate the SF project to use.
official goes to manjaro, community and minimal to manjaro-community.
I'd like to hard code the SF project names.