You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title Please consider supporting mirrors that only carry a subtree
Priority wish Status chatting
Superseder Nosy List plugwash, poeml
Assigned To Keywords
I'm using mirrorbrain for the raspbian project and while most mirrors carry our
whole tree sometimes we get mirrors which we would like to use but that only
carry part of our file tree. It would be very handy if mirrorbrain would support
this by having a prefix that is added to filenames when scanning and removed
from filenames before redirecting.
Yes, a logical approach. I had similar situations in the past, but mostly solved
them by talking to the mirror admin to change their setup, but it is often hard to
reach them, and one doesn't want to hassle them.
It requires a field in the database for storing the missing path segment, and then
using it exactly how you describe.
Existing databases need to be migrated.
History
Date User Action Args
status: unread -> chatting
2014-02-21 00:15:52 poeml set nosy: + poeml
messages: + msg549
2013-03-18 21:05:56 plugwash create
(end of migrated issue)
The text was updated successfully, but these errors were encountered:
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue121
msg422 (view) Author: plugwash Date: 2013-03-18.21:05:56
I'm using mirrorbrain for the raspbian project and while most mirrors carry our
whole tree sometimes we get mirrors which we would like to use but that only
carry part of our file tree. It would be very handy if mirrorbrain would support
this by having a prefix that is added to filenames when scanning and removed
from filenames before redirecting.
msg549 (view) Author: poeml Date: 2014-02-21.00:15:52
Yes, a logical approach. I had similar situations in the past, but mostly solved
them by talking to the mirror admin to change their setup, but it is often hard to
reach them, and one doesn't want to hassle them.
It requires a field in the database for storing the missing path segment, and then
using it exactly how you describe.
Existing databases need to be migrated.
(end of migrated issue)
The text was updated successfully, but these errors were encountered: