#463 Issue 416
Merged 4 years ago by pbokoc. Opened 4 years ago by shwetanaresh.
fedora-docs/ shwetanaresh/release-notes issue416_pascal-compiler  into  f32

@@ -0,0 +1,17 @@ 

+ == Packaging changes in clang-libs package

+ 

+ The clang-libs package now does not include the individual component libraries like libclangBasic.so, libclangAST.so and so on.

+ Packages that depend on the clang libraries are now linked to libclang-cpp.so.

+ 

+ As a result of this change,

+ 

+ * There is an improved stability in Fedora and application start-up time.

+ * End-users who develop applications using clang libraries must update their applications to use libclang-cpp.so instead of the individual component libraries.

+ However, the end-users using Fedora packages that depend on clang libraries do not have any impact of this change.

+ 

+ 

+ == Added support for AArch64 and ppc64le packages with extended availability of FPC-dependent packages

+ 

+ An updated version (3.2.0) of Free Pascal Compiler is now available with Fedora 32.

+ With the updated Free Pascal Compiler you can now build the AArch64 and ppc64le packages.

+ Also, the Free Pascal Compiler now supports new architectures. As a result, the programs that are compiled using FPC are available to run on more architectures that Fedora supports. 

rebased onto 7978844

4 years ago

Damn, that took me a while to figure out :)

I'll go ahead and merge this, but in the future, please make sure to always check out the current release branch (f32) when you start working on a new release note. It seems that you didn't do that, and instead created the branch for this PR from branch issue426_package-changes, which you created for issue #426 - and I already merged that one. Since you created the branch for this PR from another topic branch, the resulting PR included both branches, not just the one you wanted. This time it didn't cause any problems, and even if it did I can fairly easily fix that, but it's still better to avoid this situation entirely and make sure to go back to the start and check out f32 before you start working on anything new.

Pull-Request has been merged by pbokoc

4 years ago

Ah! Apologies, for the incorrect branch.
Sorry about the trouble caused.
Thanks for fixing it! I will take care next time.

Regards

Shweta

On Tue, Apr 7, 2020 at 5:24 PM Petr Bokoc pagure@pagure.io wrote:

pbokoc commented on the pull-request: Issue 416 that you are following:
``
Damn, that took me a while to figure out :)

I'll go ahead and merge this, but in the future, please make sure to
always check out the current release branch (f32) when you start workin=
g
on a new release note. It seems that you didn't do that, and instead
created the branch for this PR from branch issue426_package-changes,
which you created for issue #426 - and I already merged that one. Since y=
ou
created the branch for this PR from another topic branch, the resulting P=
R
included both branches, not just the one you wanted. This time it didn't
cause any problems, and even if it did I can fairly easily fix that, but
it's still better to avoid this situation entirely and make sure to go ba=
ck
to the start and check out f32 before you start working on anything new=
.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-docs/release-notes/pull-request/463

--=20

Shweta Naresh

Technical Writer 3, Customer Content Services

Red Hat Czech Republic https://www.redhat.com

sjalgaon@redhat.com IM: shweta
https://www.redhat.com

Metadata