On Fri, 22 Dec 2017 22:06:56 -0500,
Luke Shumaker wrote:
> > Luke Shumaker wrote :
> > > - b43-fwcutter is not replaced by, but is provided by
> > >libre/b43-tools. For one, I am flabbergasted that whatever freedom
> > >issues b43-fwcutter has aren't also issues with b43-tools.
> > >
The following is a discussion of the semantics of
provides/conflicts/replaces. It uses b43-fwcutter as an example, but
isn't about b43-fwcutter; it is written accepting the everything in my
previous email as accurate; which isn't true. What we actually should
do is keep blacklisting
On 12/22/2017 06:05 PM, Isaac David wrote:
> the idea is to get rid of replacement info in blacklist.txt
to this i want to add again that this single line of explanation in the
blacklist.txt is in most cases the only documentation of why the package
is blacklisted and what are the remedies - so
On Fri, 22 Dec 2017 17:37:03 -0500,
Isaac David wrote:
> Luke Shumaker wrote :
> > - b43-fwcutter is not replaced by, but is provided by
> >libre/b43-tools. For one, I am flabbergasted that whatever freedom
> >issues b43-fwcutter has aren't also issues with b43-tools.
> >Secondly,
On Fri, 22 Dec 2017 17:37:03 -0500,
Isaac David wrote:
>
> Luke Shumaker wrote :
> > I wrote a little pyalpm script for finding blacklist replacements (as
> > in the second column in blacklist.txt).
>
> cool. i'm eager to compare it against the one i wrote for
> libreblacklist using expac.[1][]
Megver83 wrote :
let's say we blacklist linux and linux-docs/linux-headers are
automatically blacklisted. All right up to there, but where do we
specify that linux-headers' replacement is linux-libre-headers? (same
for -docs)
in the PKGBUILD, as is currently done.
the idea is to get rid of
Luke Shumaker wrote :
I wrote a little pyalpm script for finding blacklist replacements (as
in the second column in blacklist.txt).
cool. i'm eager to compare it against the one i wrote for
libreblacklist using expac.[1][] i'm hoping that we will
move forward with the idea sketched in [2][].
El 21/12/17 a las 03:22, Luke Shumaker escribió:
> Hi guys,
>
> I wrote a little pyalpm script for finding blacklist replacements (as
> in the second column in blacklist.txt).
>
> I'll be polishing it up and committing it soon, but it did identify a
> few problems/concerns.
>
> - unrar is
i do not know the answer to any of those questions but it is good that
you looked into it so thoroughly - one thing i have been recommending
for is to ensure that each blacklisted or replaced package has some
meaningful description noting (however tersely) some rationale as to why
it was
Hi guys,
I wrote a little pyalpm script for finding blacklist replacements (as
in the second column in blacklist.txt).
I'll be polishing it up and committing it soon, but it did identify a
few problems/concerns.
- unrar is replaced by both libre/unar and pcr/gna-unrar. libre/unar
should
10 matches
Mail list logo
