On 22 September 2015 at 15:53, Andreas Cadhalpun <[email protected]> wrote: > Hi Felipe, > > On 22.09.2015 17:34, Felipe Sateler wrote: >> On 22 Sep 2015 11:23, "Andreas Cadhalpun" <[email protected]> >> wrote: >>> Exactly. The cycles involve frei0r, opencv and x264. >> >> Why not use stage1 build - profile , which is what is used by the porters >> precisely for this AFAIK? > > Are you sure these are actually used yet? > Until a month ago the infrastructure of the ports didn't even support the > build-profiles > syntax. Thus porters were actually unhappy about the build-profile support > added to x264.
But now they can handle it, so it is ok. > > And even though x264 has build-profile support for stage1, it isn't build on > mips64el, yet. > So it probably still requires manual work of the porters. Yes, it still does until the bootstrap process can be fully automated (I believe there are tools to help here, but I don't know them). If you want to help here, the correct solution is to: 1. Setup an $arch VM or use the porterbox 2. Build $package using -Pstage1 -B arguments to dpkg-buildpackage 3. Upload the resulting (limited) package 4. Rebuild packages without -Pstage1 that required $package in !stage1 And rinse and repeat 2-4 for each package involved as long as any package has unresolvable build-depends. I would suggest contacting the porters first though, as multimedia codecs are not likely to be the first priority. Perhaps adding more packages to the build queue actually hinders their progress! -- Saludos, Felipe Sateler _______________________________________________ pkg-multimedia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
