Timeline for Best practices for packaging self created software for Debian
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2013 at 22:23 | comment | added | Faheem Mitha | I had initially thought of just having the debian packaging in a separate branch, and merging the code and the packaging in a third temporary branch, but the opinion seemed to be that this was too many branches. Thoughts? | |
| Jul 29, 2013 at 19:31 | comment | added | jofel | @FaheemMitha Yes, this is totally fine. In first place, get-orig-source is for you as the maintainer, and secondly for others, who wants to re-create the orig-tarball. | |
| Jul 29, 2013 at 19:07 | comment | added | Faheem Mitha | Thanks for the comments. Since some of the time the debian packaging will be in a mercurial repos, i was wondering if it made sense to try hg archive on the assumption that the source is available locally, i.e. without a local clone, and if that failed, clone the repository from remote. Is this done? The examples on github I looked at don't seem to do this. | |
| Jul 29, 2013 at 18:43 | history | answered | jofel | CC BY-SA 3.0 |