[haiku-development] Re: reviving R1/Alpha2 & R1 Final discussions.

On Wed, Mar 17, 2010 at 18:46, Rene Gollent <anevilyak@xxxxxxxxx> wrote:
...   <about Layout API & Locale API being final/public API>
> We could do something like what Be did where they're available in an
> experimental namespace to indicate that they may not stay ABI-stable
> in the future.
>
Assuming those API's aren't finished by R1 Final, would this be acceptable?
Also, would it be possible for those API's to be experimental in Beta
K and be moved up to a final & public API in Beta K+1 ?


On Wed, Mar 17, 2010 at 19:17, Rene Gollent <anevilyak@xxxxxxxxx> wrote:
> On Wed, Mar 17, 2010 at 3:04 PM, Stephan Assmus <superstippi@xxxxxx> wrote:
>> For libpng, I am not sure if we have a binary compat issue. IIRC, libpng was
>> provided by BeOS. The library that we now provide as "libpng.so" has a
>> different ABI. But I am not aware of any apps that directly used this, and
>> which cannot be rebuilt.
>
> The only apps using it directly should be things like WebKit and
> Bezilla AFAIK...at least actual native apps generally just use
> PNGTranslator which hides the ABI compat issue anyhow, no?

I've already rebuilt Bezilla to use its own libpng, iirc it's part of
a larger library which in turn get statically linked into the
executable. Seeing as how far Web+ has come along, I'd rather not
invest time into bezilla to get it to use the new png API.


On Wed, Mar 17, 2010 at 20:08, scott mc <scottmc2@xxxxxxxxx> wrote:
>On Wed, Mar 17, 2010 at 19:04, Stephan Assmus <superstippi@xxxxxx> wrote:
>> As far as packaging goes, I am not sure if we need to repackage all packages
>> like we did for the alpha. I would just rebuild those packages which got
>> broken by updates to Haiku components.

IIRC, we add some ABI version information inside the release branches,
which necessitates rebuilding.

> I've been going through the optionalpackages making sure they have
> working .bep files files on HaikuPorts so that we can easily rebuild
> them:
> http://dev.haiku-os.org/wiki/R1/Alpha2/OptionalPackages

As a reminder, when rebuilding the packages, it'd be much preferred to
archive the patched sources too.

I've been thinking .. maybe it's possible for HaikuPorter to generate
the .OptionalPackageDescription file on-the-fly. The individual .beps
could be extended to include that information. This would then help to
auto-generate the SourceURL: Text <url> fields.

--mmadia

Other related posts: