Really important work there... nothing gets me out of bed like
suppressing someone else's future potential needs using crappy tools and
methodologies.
This isn't a criticism of Debian. Use the Debian system if you like it,
don't use it if you don't.
It is a criticism of Debian in Wireshark,
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-impor
Hi
I would recommend that we bring this topic before the technical steering
committee. As of right now, that committee needs to be formed in
January and this topic is exactly why we are going to have the committee in
the first place. The process is in the final steps and should be finished
by the
Hi,
I think that if you look at the commit history I have made my fair share of
updating the list in the past.
I was just trying to make the point that some found it useful to be able to
build Deb packages and it might be more fruitful to discuss how that could
be made easier? I think today the sc
You are free to participate in the discussion or not. But I really don't
care to wait for the new committee that is pretty much exactly the same
as the old committee, as far as I can tell.
Anyway silence is another Wireshark project classic. At least you tried
to bring something to the debate,
Hi Joao,
Le mer. 22 nov. 2023 à 14:01, João Valverde a écrit :
> You are free to participate in the discussion or not. But I really don't
> care to wait for the new committee that is pretty much exactly the same as
> the old committee, as far as I can tell.
>
> Anyway silence is another Wireshar
So you want to discuss how to make it easier? We can do that. How do you
feel about the CPack Debian Generator?
On 22/11/23 12:38, Anders Broman wrote:
Hi,
I think that if you look at the commit history I have made my fair
share of updating the list in the past.
I was just trying to make the
Pretty sure I'm not adding anything useful here, but I was only vaguely
aware of debian packaging support. If I'm sharing builds with colleagues,
I use Windows packaging, or for Ubuntu we tend to set CMAKE_INSTALL_PREFIX,
build the 'install' target and transfer it as a tarball.
On Wed, Nov 22, 20
On 22/11/23 13:12, Pascal Quantin wrote:
Hi Joao,
Le mer. 22 nov. 2023 à 14:01, João Valverde a écrit :
You are free to participate in the discussion or not. But I really
don't care to wait for the new committee that is pretty much
exactly the same as the old committee, as far as
Le mer. 22 nov. 2023 à 14:25, João Valverde a écrit :
>
> On 22/11/23 13:12, Pascal Quantin wrote:
>
> Hi Joao,
>
> Le mer. 22 nov. 2023 à 14:01, João Valverde a écrit :
>
>> You are free to participate in the discussion or not. But I really don't
>> care to wait for the new committee that is pr
On 22/11/23 13:29, Pascal Quantin wrote:
Le mer. 22 nov. 2023 à 14:25, João Valverde a écrit :
On 22/11/23 13:12, Pascal Quantin wrote:
Hi Joao,
Le mer. 22 nov. 2023 à 14:01, João Valverde a écrit :
You are free to participate in the discussion or not. But I
On 22/11/23 13:23, Martin Mathieson via Wireshark-dev wrote:
Pretty sure I'm not adding anything useful here, but I was only
vaguely aware of debian packaging support. If I'm sharing builds with
colleagues, I use Windows packaging, or for Ubuntu we tend to set
CMAKE_INSTALL_PREFIX, build the
On 22/11/23 13:12, Pascal Quantin wrote:
Hi Joao,
Le mer. 22 nov. 2023 à 14:01, João Valverde a écrit :
You are free to participate in the discussion or not. But I really
don't care to wait for the new committee that is pretty much
exactly the same as the old committee, as far as
On 22/11/23 14:39, João Valverde wrote:
On 22/11/23 13:12, Pascal Quantin wrote:
Hi Joao,
Le mer. 22 nov. 2023 à 14:01, João Valverde a écrit :
You are free to participate in the discussion or not. But I
really don't care to wait for the new committee that is pretty
much exact
On Wed, Nov 22, 2023 at 9:40 AM João Valverde wrote:
>
> There are a myriad issues I have touched upon. To recap, in my opinion, if
> we want to provide public shared libraries (libwireshark, wiretap,
> wsutil... for what I don't know) we should do a better job of that
> collectively as a project
On Wed, Nov 22, 2023 at 10:37 AM John Thacker wrote:
>
> I think moving the packaging assets to the packaging directory and telling
> people to symbolically link it to build Debian, as we've been doing, is a
> relatively minor imposition for the Debian folks, but my understanding is
> that the pa
On 22/11/23 15:37, John Thacker wrote:
On Wed, Nov 22, 2023 at 9:40 AM João Valverde wrote:
There are a myriad issues I have touched upon. To recap, in my
opinion, if we want to provide public shared libraries
(libwireshark, wiretap, wsutil... for what I don't know) we should
I think this falls well within the scope of the steering committee, and would
be a good first exercise.
On 11/22/23 3:45 AM, Roland Knall wrote:
Hi
I would recommend that we bring this topic before the technical steering
committee. As of right now, that committee needs to be formed in January
18 matches
Mail list logo
