#3212: Avahi-0.6.28
----------------------------------------+-----------------------------------
Reporter: ra...@… | Owner: blfs-b...@…
Type: defect | Status: new
Priority: high | Milestone: 6.7
Component: BOOK | Version: SVN
Severity: major | Keywords:
----------------------------------------+-----------------------------------
Comment(by ra...@…):
William,
I appreciate your interest in the avahi project and your willingness to
provide LFS style initscripts upstream. However, you have self-admitted
that upstream is not interested in any more patches, so we would have to
continually update the patch (even if just a name change) and run
autoreconf every time there is a version update to avahi.
The BLFS bootscripts should be maintained in a single project file so that
if changes are required globally to the bootscripts (make them LSB
compliant, for example), we can do it easily and ensure that all the
bootscripts are touched accordingly. The last thing we want to do is to
have to create a patch to an upstream project when we could (and should)
be maintaining it ourselves.
All the BLFS packages that require bootscripts are included in the single
blfs-bootscripts file. This is the preferred method because it is less
work for the editors every time there is an avahi update, it is consistent
with all BLFS packages, and we don't have to patch upstream packages.
Please, I understand you do not like this decision, however two BLFS
editors have agreed that our maintaining the avahi bootscripts is the best
overall solution, so at this point until something changes, let's drop the
subject and move on. It would be helpful if you could provide a patch to
the BLFS bootscripts themselves to include scripts for the avahi package.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/3212#comment:7>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page