Maybe you´d like to volunteer to maintain the Wireshark Debian assets? Since you've got the experience and actually use it?

There are loads of lintian warnings waiting to be fixed, or there were until recently. Maybe you'd like to start there, and be more active staying on top of the all-important symbol lists. Just a thought.

On 21/11/23 15:00, Anders Broman wrote:
Hi,
I found it useful to be able to do Debian packages easily to provide internal installation packages and even ppa for Ubuntu.
So I have been using the Debian build system.
Best regards
Anders

Den tis 21 nov. 2023 15:48Roland Knall <rkn...@gmail.com> skrev:

    As mentioned on the ticket - just putting it here as well - I am
    against dropping packaging/debian. But I am for having it
    underneath packaging, and not in the main directory, which is what
    the original change was about. I respect Joao's opinion as well as
    yours Balint. In this case here I think, we can provide assistance
    for future implementors and as a starting point, by keeping the
    directory underneath packaging/debian.

    just my thoughts
    Roland


    Am Di., 21. Nov. 2023 um 15:28 Uhr schrieb Bálint Réczey
    <bal...@balintreczey.hu>:

        Hi All,

        João shared his opinion about the project's commitment to
        maintain the
        packaging/debian/ in the project's repository:

        
https://gitlab.com/wireshark/wireshark/-/commit/79da670bd1b4f91eebee5c96b19eaf1f33c94777#note_1656501952

        I believe the current practice is reasonable and beneficial
        enough for
        many parties to warrant the work, but I could be wrong.

        Probably the most important question is if there is anyone
        relying on
        the packaging scripts there. If you are, please speak up
        otherwise the
        directory may be dropped.

        Comments are welcome.

        Cheers,
        Balint
        
___________________________________________________________________________
        Sent via:    Wireshark-dev mailing list
        <wireshark-dev@wireshark.org>
        Archives: https://www.wireshark.org/lists/wireshark-dev
        Unsubscribe:
        https://www.wireshark.org/mailman/options/wireshark-dev
                   
         mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

    ___________________________________________________________________________
    Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
    Archives: https://www.wireshark.org/lists/wireshark-dev
    Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
               
     mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list<wireshark-dev@wireshark.org>
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe:https://www.wireshark.org/mailman/options/wireshark-dev
              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to