[tsc-devel] Providing an APT repository on alexandria (new team member?)

Marvin Gülker | Sun, 16 Sep 2018 19:53:04 UTC

Hi everyone,

there is a user on our tracker, boospy, who has built a .deb package
from Ubuntu 18.04 from TSC's `devel' branch[1]. I've asked him whether
he'd be willing to continue package building for future versions, and he
agreed, so I think we should consider the following.

For one, we should give boospy (limited, for now, i.e. please no sudo
rights) access to alexandria so he can move his APT repository over
there. If we officially endorse an APT repository for installing TSC
packages, then the APT repository should be hosted on our domain and
infrastructure. For this, boospy needs the required access.

I assume he's using reprepro to provide the repository, which should be
doable easily on alexandria as well.

For the other, I think it does not make sense to grant access to our
server to someone who isn't on the TSC team, so I think boospy should be
added to the Secretchronicles GitHub organisation if we decide to go
this way.

Finally, the details on the packaging process need a little
discussion. Since there's no release immediately in sight, I suppose for
now it is enough to have builds from the `devel' branch (maybe automated
nightlies?). Once we get around to a 2.1 release, we'll need to
reconsider what should be packaged when. I suggest that the packages
from the `devel' branch however should right from the start have a name
different from "TSC", because that name should be reserved for a future
stable release series. Maybe "TSC2.1-unstable"?

Please voice your opinion on these topics. I realise that giving access
rights to a random person is probably not a good idea, but I'm not
familiar enough with APT nor .deb packaging to evaluate other
possibilities. Any discussion is appreciated.

Marvin

[1]: https://github.com/Secretchronicles/TSC/issues/637

-- 
Blog: https://mg.guelker.eu
PGP/GPG ID: F1D8799FBCC8BC4F
_______________________________________________
tsc-devel mailing list -- …l@l…
To unsubscribe send an email to …e@l…