Hi guys, we really need to redo the current binaries for libreoffice, the provided RPMs fail miserably by providing everything bundled inside, including fancy stuff like python, zlib to cairo... So my idea would be to generate the -bin for stable tree from our libreoffice ebuild. We would need to build just few variants to make almost everyobody happy: graphite -java -gtk -gnome -eds kde templates branding binfilter graphite -java gtk -gnome -eds -kde templates branding binfilter graphite -java gtk gnome eds -kde templates branding binfilter graphite java -gtk -gnome -eds kde templates branding binfilter graphite java gtk -gnome -eds -kde templates branding binfilter graphite java gtk gnome eds -kde templates branding binfilter I would say target archs would be amd64 and x86. So what do you think, is my request even possible?
flameeyes: why did you include infra in this?
(In reply to comment #1) > flameeyes: why did you include infra in this? It is not bug opened by Diego but by me. And Christian told me to do so and cc Jorge and Diego...
(In reply to comment #0) > So what do you think, is my request even possible? Eventually, we plan to offer hw availability for devs to manage. One this to note: - infra doesn't have the manpower to monitor services like this, so infra would provide the hw and devs (you) would use it as you see fit I guess we will leave this bug open for now but it doesn't have an ETA (yet) for resolution. PS. Ask the chromium guys how well it went to build the -bin packages themselves (hint: it didn't go well) Hope you have a good plan ;)
(In reply to comment #3) > Eventually, we plan to offer hw availability for devs to manage. Eventually, we plan to offer hw availability for devs to utilize*
(In reply to comment #4) > (In reply to comment #3) > > > Eventually, we plan to offer hw availability for devs to manage. > > Eventually, we plan to offer hw availability for devs to utilize* Well
(In reply to comment #5) > Well Oh, cmon. We would let you know if something was ready...
(In reply to comment #6) > (In reply to comment #5) > > > Well > > Oh, cmon. We would let you know if something was ready... Sorry that was an unintended comment :] What I actually wanted to write, apart from cc'ing openoffice: Well we do generate the packages ourselves now, and so far it seems to work out fine. On the other hand generating a full set of packages takes one night on my i7 and even less on quantumsummer's ec2 instance, so I dont see having a vm as urgent problem at the moment.
I'm going to combine this with 429702. *** This bug has been marked as a duplicate of bug 429702 ***