Re: Intention to retire mlocate
Christopher wrote on Fri, May 24, 2024 at 02:15:17AM -0400: > A flag to treat the arguments as OR like mlocate did instead of the default > to AND would be great, though I wish plocate would have more closely > mimicked mlocate's default behavior from the beginning and had a flag for > AND instead. Unfortunately, one cannot go back in time. Here's the reply from Steinar: > for OR searches, you can either use --regex, or call plocate multiple times > this is the one deliberate incompatibility between mlocate and plocate, and > it's not going to be changed :-) > both will be slow, but OR-searches are going to be slow anyway (I've added a working mail this time; will let you (Christopher) argue directly if you want to continue, I don't care enough) -- Dominique Martinet | Asmadeus -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
Christopher wrote on Fri, May 24, 2024 at 02:18:04AM -0400: > Are you sure you have the correct address for the plocate developer and > that it's still actively maintained? I just got an error that the > destination email address didn't exist from their mail server when I > replied just now. Yeah, I reached out over irc after sending that mail but not answer yet -- the repo is still active (there was a new release earlier this year), I just decided to drop the '+git' from the mail he uses in his commit messages and his server apparently doesn't like addresses without the + suffix, so that was probably my mistake here but it's not clear where he wants bug reports from [1], probably +web I guess... [1] https://plocate.sesse.net/ I've given him a link to this thread on IRC, so he'll hopefully reply when he checks it. -- Dominique -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
Are you sure you have the correct address for the plocate developer and
that it's still actively maintained? I just got an error that the
destination email address didn't exist from their mail server when I
replied just now.
On Fri, May 24, 2024, 02:15 Christopher wrote:
> A flag to treat the arguments as OR like mlocate did instead of the
> default to AND would be great, though I wish plocate would have more
> closely mimicked mlocate's default behavior from the beginning and had a
> flag for AND instead. Unfortunately, one cannot go back in time.
>
> On Thu, May 23, 2024, 20:04 Dominique Martinet
> wrote:
>
>> Christopher wrote on Thu, May 23, 2024 at 06:26:57PM -0400:
>> > One thing I've noticed is that plocate behaves differently when
>> > supplied with multiple arguments than mlocate. This broke some of my
>> > scripts.
>> >
>> > Previously, I had:
>> >
>> > locate rpm{old,new,save,orig,moved}
>> > # expands to locate rpmold rpmnew rpmsave rpmorig rpmmoved
>> >
>> > But now, I need to do:
>> >
>> > for x in rpm{old,new,save,orig,moved}; do locate "$x"; done
>> >
>> > The frustrating part is that it didn't even break in an obvious way.
>> > It just ignored all the arguments after the first one, so it was only
>> > searching for rpmold, and ignored all the others.
>> >
>> > In this way (and perhaps only this way?), mlocate was better. plocate
>> > should handle these arguments, or at least fail with a message letting
>> > you know that it is ignoring the rest of the arguments.
>>
>> Looking at the code[1], it's supported multiple arguments since 1.0.0
>> (2020) so basically forever as far as fedora is concerned; but while
>> mlocate was looking for each argument individually (according to your
>> report) plocate is adding, plocate is looking for files that match all
>> the arguments given; so it's a pretty extreme change of behaviour...
>>
>> At this point changing it will break scripts for people used to the new
>> plocate behaviour, so I'm not sure there's a good solution here - perhaps
>> a new switch that'll toggle whether we want matches for all the words
>> (plocate behaviour) or all matches for each words (mlocate behaviour)?
>>
>> Either way, it's something to report upstream so I've added Steinar in
>> Ccs.
>>
>> [1] https://git.sesse.net/?p=plocate
>> --
>> Dominique Martinet | Asmadeus
>> --
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>> Do not reply to spam, report it:
>> https://pagure.io/fedora-infrastructure/new_issue
>>
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
A flag to treat the arguments as OR like mlocate did instead of the default
to AND would be great, though I wish plocate would have more closely
mimicked mlocate's default behavior from the beginning and had a flag for
AND instead. Unfortunately, one cannot go back in time.
On Thu, May 23, 2024, 20:04 Dominique Martinet
wrote:
> Christopher wrote on Thu, May 23, 2024 at 06:26:57PM -0400:
> > One thing I've noticed is that plocate behaves differently when
> > supplied with multiple arguments than mlocate. This broke some of my
> > scripts.
> >
> > Previously, I had:
> >
> > locate rpm{old,new,save,orig,moved}
> > # expands to locate rpmold rpmnew rpmsave rpmorig rpmmoved
> >
> > But now, I need to do:
> >
> > for x in rpm{old,new,save,orig,moved}; do locate "$x"; done
> >
> > The frustrating part is that it didn't even break in an obvious way.
> > It just ignored all the arguments after the first one, so it was only
> > searching for rpmold, and ignored all the others.
> >
> > In this way (and perhaps only this way?), mlocate was better. plocate
> > should handle these arguments, or at least fail with a message letting
> > you know that it is ignoring the rest of the arguments.
>
> Looking at the code[1], it's supported multiple arguments since 1.0.0
> (2020) so basically forever as far as fedora is concerned; but while
> mlocate was looking for each argument individually (according to your
> report) plocate is adding, plocate is looking for files that match all
> the arguments given; so it's a pretty extreme change of behaviour...
>
> At this point changing it will break scripts for people used to the new
> plocate behaviour, so I'm not sure there's a good solution here - perhaps
> a new switch that'll toggle whether we want matches for all the words
> (plocate behaviour) or all matches for each words (mlocate behaviour)?
>
> Either way, it's something to report upstream so I've added Steinar in Ccs.
>
> [1] https://git.sesse.net/?p=plocate
> --
> Dominique Martinet | Asmadeus
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
Christopher wrote on Thu, May 23, 2024 at 06:26:57PM -0400:
> One thing I've noticed is that plocate behaves differently when
> supplied with multiple arguments than mlocate. This broke some of my
> scripts.
>
> Previously, I had:
>
> locate rpm{old,new,save,orig,moved}
> # expands to locate rpmold rpmnew rpmsave rpmorig rpmmoved
>
> But now, I need to do:
>
> for x in rpm{old,new,save,orig,moved}; do locate "$x"; done
>
> The frustrating part is that it didn't even break in an obvious way.
> It just ignored all the arguments after the first one, so it was only
> searching for rpmold, and ignored all the others.
>
> In this way (and perhaps only this way?), mlocate was better. plocate
> should handle these arguments, or at least fail with a message letting
> you know that it is ignoring the rest of the arguments.
Looking at the code[1], it's supported multiple arguments since 1.0.0
(2020) so basically forever as far as fedora is concerned; but while
mlocate was looking for each argument individually (according to your
report) plocate is adding, plocate is looking for files that match all
the arguments given; so it's a pretty extreme change of behaviour...
At this point changing it will break scripts for people used to the new
plocate behaviour, so I'm not sure there's a good solution here - perhaps
a new switch that'll toggle whether we want matches for all the words
(plocate behaviour) or all matches for each words (mlocate behaviour)?
Either way, it's something to report upstream so I've added Steinar in Ccs.
[1] https://git.sesse.net/?p=plocate
--
Dominique Martinet | Asmadeus
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
One thing I've noticed is that plocate behaves differently when
supplied with multiple arguments than mlocate. This broke some of my
scripts.
Previously, I had:
locate rpm{old,new,save,orig,moved}
# expands to locate rpmold rpmnew rpmsave rpmorig rpmmoved
But now, I need to do:
for x in rpm{old,new,save,orig,moved}; do locate "$x"; done
The frustrating part is that it didn't even break in an obvious way.
It just ignored all the arguments after the first one, so it was only
searching for rpmold, and ignored all the others.
In this way (and perhaps only this way?), mlocate was better. plocate
should handle these arguments, or at least fail with a message letting
you know that it is ignoring the rest of the arguments.
--
Christopher
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
On Tue, May 21, 2024 at 01:19:24PM +0200, Miro Hrončok wrote: > On 21. 05. 24 12:29, Fabio Valentini wrote: > > On Mon, May 20, 2024 at 2:42 PM Michal Sekletar wrote: > > > > > > On Fri, May 17, 2024 at 6:14 PM Michal Sekletar > > > wrote: > > > > > > > > Hi everyone, > > > > > > > > We have had a plocate as a drop-in replacement for mlocate for quite a > > > > while now. My intention is to retire the mlocate package next week in > > > > order to prevent duplication and so that we can focus only on plocate > > > > going forward. > > > > > > > > > mlocate is now retired in Rawhide. > > > > > > https://src.fedoraproject.org/rpms/mlocate/c/7277dd5f59db126d1046a6aa5c4077a597dc?branch=rawhide > > > > Thanks for the heads-up! > > Should the package also be added to fedora-obsolete-packages so that > > it is - if installed - removed on upgrade to Fedora 41? > > If a specific replacement exists (plocate), I think it should Obsolete it > explicitly. It already does. Zbyszek -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
On 21. 05. 24 12:29, Fabio Valentini wrote: On Mon, May 20, 2024 at 2:42 PM Michal Sekletar wrote: On Fri, May 17, 2024 at 6:14 PM Michal Sekletar wrote: Hi everyone, We have had a plocate as a drop-in replacement for mlocate for quite a while now. My intention is to retire the mlocate package next week in order to prevent duplication and so that we can focus only on plocate going forward. mlocate is now retired in Rawhide. https://src.fedoraproject.org/rpms/mlocate/c/7277dd5f59db126d1046a6aa5c4077a597dc?branch=rawhide Thanks for the heads-up! Should the package also be added to fedora-obsolete-packages so that it is - if installed - removed on upgrade to Fedora 41? If a specific replacement exists (plocate), I think it should Obsolete it explicitly. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
On Mon, May 20, 2024 at 2:42 PM Michal Sekletar wrote: > > On Fri, May 17, 2024 at 6:14 PM Michal Sekletar wrote: >> >> Hi everyone, >> >> We have had a plocate as a drop-in replacement for mlocate for quite a while >> now. My intention is to retire the mlocate package next week in order to >> prevent duplication and so that we can focus only on plocate going forward. > > > mlocate is now retired in Rawhide. > > https://src.fedoraproject.org/rpms/mlocate/c/7277dd5f59db126d1046a6aa5c4077a597dc?branch=rawhide Thanks for the heads-up! Should the package also be added to fedora-obsolete-packages so that it is - if installed - removed on upgrade to Fedora 41? Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Intention to retire mlocate
On Fri, May 17, 2024 at 6:14 PM Michal Sekletar wrote: > Hi everyone, > > We have had a plocate as a drop-in replacement for mlocate for quite a > while now. My intention is to retire the mlocate package next week in order > to prevent duplication and so that we can focus only on plocate > going forward. > mlocate is now retired in Rawhide. https://src.fedoraproject.org/rpms/mlocate/c/7277dd5f59db126d1046a6aa5c4077a597dc?branch=rawhide > > Have a nice weekend, > Michal > -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Intention to retire mlocate
Hi everyone, We have had a plocate as a drop-in replacement for mlocate for quite a while now. My intention is to retire the mlocate package next week in order to prevent duplication and so that we can focus only on plocate going forward. Have a nice weekend, Michal -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
