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

Sydney Dykstra | Thu, 20 Sep 2018 15:44:50 UTC

Greetings,

 Sweet, it is cool to see that someone is willing to maintain a APT
repository for us.

 First off,  I don't mind that he is trying to create a PPA(Personal
Package Archive, as Ubuntu calls it). As a matter of fact, I think it is
a good thing. I know alot of people in the Debian ecosystem frown on the
practice of adding unknown repositories to systems, whereas people in
the Ubuntu ecosystem seem to almost recommend it. I personally don't
care so long as it doesn't break my package manager and it seems to be a
reputable source link. It would probably make the most sense just to
create a Ubuntu PPA, and not try to support Debian.

 As for naming regime, TSC2.1-devel or -unstable would be a wise choice,
so we don't accidentally break anybody's package manager in the future.

 It would also be wise to add him to the Github organization before we
grant him server access, just to show that he is part of the team. After
we have done that I can create a user account for him on Alexandria.
This is debatable, but I prefer that he is an official team member
before creating an account for him.


Those are my thoughts on the subject. We do need to have more team input
before going further though.


Have a great day team!

-Sydney


On 9/16/18 3:53 PM, Marvin Gülker wrote:
> 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

>

_______________________________________________
tsc-devel mailing list -- …l@l…
To unsubscribe send an email to …e@l…