[Hamara-devel] Approach for Packaging in Hamara 2.0 "Svastik"

Pirate Praveen praveen at onenetbeyond.org
Sat Aug 25 20:20:22 IST 2018


On ശനി 25 ഓഗസ്റ്റ് 2018 07:23 വൈകു, Vikas Tara wrote:
> Hi,
> 
> This is something that needs to be finalised still.
> 
> We are proposing basing on debian testing so that there are newer
> packages than stable.

Another option is going stable + backports, in that case a subset of
newer packages in unstable will be available based on popularity.

> However there are quite a few things which are not yet packaged in
> debian testing but will be as it comes closer to stable.
> 
> Unstable often does have the packages, but unstable is not recommended
> for everyday use.

When a package is in unstable but not in testing, usually it means there
is a release critical bug or it can break other packages in testing.

> We have also talked about having our own testing repo in between
> upstream and our live repo. We would be able to maintain a test version
> of svastik that way.

Even in that case, either you have to compromise on bugs or will have to
choose a subset. For example take ruby-sanitize (a package that I worked
on recently). It had version 2 in testing which has a security bug,
unstable had version 4 for some time, but there were other packages in
testing which were not ready yet for sanitize 4. I had to make sure all
packages are made compatible with sanitize version 4 before I got it
into testing. I don't think your own repo will solve this case unless
you have to choose only a subset of packages in that case the effort to
ensure compatibility will also reduce.

> We have some options here to help fill the gaps:
> 
> 1. work with (and encourage more people to become) debian developers to
> help move things from unstable to testing to help meet our own release
> cycle (good for everyone)

+1
> 2. where that is not possible, use flatpak/snap approach to package
> things from either stable or unstable

Be warned that, it means duplication, because you will have keep
maintaining multiple versions of libraries (one for apt and another for
flatpack).

> 3. ideas where 1 and 2 are not possible?
> 
> Any other comments / ideas?

I think it would be good to join forces with PurOS and LMDE to share the
work load. I think LMDE has a stabilizing repo between LMDE and debian
testing.

> 
> 
> Vik
> 
> _______________________________________________
> Hamara-devel mailing list
> Hamara-devel at lists.hamaralinux.org
> http://lists.hamaralinux.org/listinfo/hamara-devel
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.hamaralinux.org/pipermail/hamara-devel/attachments/20180825/2860bd14/attachment.sig>


More information about the Hamara-devel mailing list