W.r.t. the things below: maybe we should reach out to the ports/pkgsrc/homebrew people and see what's possible.

Is there an easy way to figure out who we should try and talk to during FOSDEM?


K.

On 12/27/2012 02:04 PM, Fotis Georgatos wrote:
Hi Kenneth et al,

(changing the scope of the reply both in To: and Subject: )

On 27 Dec, 2012, at 09:11, Kenneth Hoste wrote:
No EasyBuild lightning talk on the general track of FOSDEM...
No problem; Plenty of chance to exploit other FOSDEM options!
btw. my HPCBIOS MC/CIG grant didn't make it through the EU process either
(chances were 1 in 10... better to just try again in other slots!)

For FOSDEM though, we should join forces with the groups that do package 
management
in general (or ports, of any style). I notice that there is too much overlap of 
work
among open source groups, so it's optimal to swap info; eg. I wouldn't believe 
there is
no common interest among *ports/pkgsrc/homebrew... deb/opensuse/rpm... and 
easybuild,
to automate a few things together or reduce work for the newcomers.

fyi.
While playing with more recent pkgsrc-to-easybuild experiments, I noticed a few 
things:
(ref: 
https://github.com/fgeorgatos/easybuild.experimental/tree/master/contrib/pkgsrc)
* trivial packages derive automatically without much fuss (m4, zlib, gzip, 
tcsh, lib*)
   this can prove very useful for fast-feeding small dependencies of bigger 
packages
* Sometimes, automated package generation IS faster/better than a manual one 
(ex.: SDCC!);
   I guess this is just me failing to spend enough time on the documentation of 
a package
* Certain packages, like clang, modify eg. the release tarball name across 
versions...
   ... why repeat such trivial work across so many teams? There must be a 
better way.

ps.
Of course, EasyBuild has a different scope (HPC) than most other build systems,
so you may find this an exercise in vain. Nevertheless, if there is overlap of 
work,
it would be interesting to, at least, know what that is.

with best wishes for the new year to all,

Fotis

Reply via email to