Tarballs is also an option, and one of the final port differences is, my Trinity_RPM
edition will require an install of RPM, whose base OS project is PCLinuxOS
And your Trinity_tarballs
edition requires nothing not native, so both editons will be found in my personal ports of a FreeBSD LiveDVD project
I.e. Trinity_RPM
and Trinity_tarballs
are supposed to be the mutual mirrors, which both trees are hosted on the same official Trinity TDE project
Also, i have Liri shell coming from Linux to be put into my FreeBSD port trees for that same LiveDVD project, and their official Git trees on GitHub are used
Having done everything above for uploads exclusively uses Git serrvices
PS: Liri shell is written firstly for Fedora also packaging by RPM, but every 3 years RPM sources die 4 times, too unstable for static porting, so only Git trees are used for porting Liri shell
My porting expects online to online direct porting, only when those ports are being installed by an user, or whose source Git trees or RPM sources or tarballs will never be downloaded
When whose deps also come from those Git trees or source archives themselves, active installs and deps will also be downloaded together after an install instruction by an user starts running