option to create torrent #238

Closed
opened 2016-07-12 18:32:25 +00:00 by philm · 4 comments
philm commented 2016-07-12 18:32:25 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

move torrent creation from deployiso to buildiso

*Created by: udeved* move torrent creation from deployiso to buildiso
philm commented 2016-07-12 18:33:48 +00:00 (Migrated from gitlab2.manjaro.org)

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: philmmanjaro* Does this make sense to do so? I thought http seed should be part of our torrents. How should that **buildiso** know?
philm commented 2016-07-12 18:37:09 +00:00 (Migrated from gitlab2.manjaro.org)

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* 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?
philm commented 2016-07-12 18:38:51 +00:00 (Migrated from gitlab2.manjaro.org)

Created by: udeved

Oh. its easy to make buildiso know the webseed url from manjaro-tools.conf ;)

*Created by: udeved* Oh. its easy to make buildiso know the webseed url from manjaro-tools.conf ;)
philm commented 2016-07-12 18:52:19 +00:00 (Migrated from gitlab2.manjaro.org)

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.

*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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
tools/manjaro-tools#238
No description provided.