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
{{ message }}
This repository has been archived by the owner on Aug 6, 2023. It is now read-only.
When channe list growing, It's really hard to export channel list from one machine to another. there is no quick way to export/import channel list.
My idea is from Debian's sources.list, users can have many package sources (just like PEAR channel source), pyrus can use this source list to update / upgrade packages very easily.
But I think It's better to design another component to manipulate channel list data, and put channel list info under user's $HOME/.pyrus directory or something , may store in JSON format, so applications can manipulate these data very easily.
If pyrus can accept this, I am glad to design such component and provide a API , documentation to support Pyrus. :-)
The text was updated successfully, but these errors were encountered:
When channe list growing, It's really hard to export channel list from one machine to another. there is no quick way to export/import channel list.
My idea is from Debian's sources.list, users can have many package sources (just like PEAR channel source), pyrus can use this source list to update / upgrade packages very easily.
But I think It's better to design another component to manipulate channel list data, and put channel list info under user's $HOME/.pyrus directory or something , may store in JSON format, so applications can manipulate these data very easily.
If pyrus can accept this, I am glad to design such component and provide a API , documentation to support Pyrus. :-)
The text was updated successfully, but these errors were encountered: