#1538 libnet10-1.0.2a-17.fc11 should be tagged into dist-f11
Closed: Fixed None Opened 14 years ago by robert.

libnet10-1.0.2a-17.fc11 should be tagged into dist-f11: That build enables the shared library of libnet10 and removes the static library. As dynamic libraries always should be preferred, I would like to see that package tagged into dist-f11 for final.

Currently only one package (snort) statically links against libnet10, that package could be also made dynamically linking if we do a buildroot override and also tag that snort build into dist-f11. That would be the perfect case.

But another package (sing) is currently in review and I would like to see that package already dynamically linked against libnet10 - even if sing has to go its way into Fedora via Bodhi (I assume, newpackage is no reason for breaking freeze as well?).

Libnet10 code is still the same, just build with a shared library. Snort on Rawhide is already build against dynamic libnet10 and seems to work so far. Sing works also as expected with dynamic libnet10 linking in my test environment.

If package doesn't get tagged into dist-f11, snort will be static linked and I have to push libnet10 via Bodhi and afterwards sing. Because of less package dependencies there should be less risk or issues when doing the tagging now. It just lowers the zero-day updates.


Metadata Update from @robert:
- Issue set to the milestone: Fedora 11 Preview

7 years ago

Login to comment on this ticket.

Metadata