Comment # 14
on bug 8190
from Anders Broman
(In reply to comment #13)
> (In reply to comment #12)
> > (In reply to comment #10)
> > > (In reply to comment #9)
> >
> > >
> > > BTW it would be nice to collect a few reasons why keeping the /debian dir
> > > seems to be the better idea. Just for the record. :-)
> >
> > For one: http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcBinary.html
> > Now it's just a one-liner: make debian-package to build your own packages.
> > This (and the RPM chapter) will have to be expanded on how to do / set this
> > up with other resources before we start ripping out packaging files.
>
> If you're an end-user you should be getting your packages from upstream
> (debian, fedora, etc.). If you're a maintainer you're used to building your
> own packages. I'm not immediately seeing a use case for non-maintainers that
> want to build their own custom packages from trunk?
How about corporations wanting to do internal custom builds including
proprietarry dissectors/plugins using top of trunk?
You are receiving this mail because:
- You are watching all bug changes.