Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #11579 > unrolled thread

jflex package

Back to article view | Back to linux.debian.maint.java

Contents

  jflex package Gilles Filippini <pini@debian.org> - 2020-04-25 18:00 +0200
    Re: jflex package Markus Koschany <apo@debian.org> - 2020-04-26 00:00 +0200
      Re: jflex package Gilles Filippini <pini@debian.org> - 2020-04-26 01:20 +0200
        Re: jflex package Markus Koschany <apo@debian.org> - 2020-04-26 14:10 +0200

#11579 — jflex package

[Multipart message — attachments visible in raw view] — view raw

Hi,

Is the jflex package still maintained? It has no upload since 2018 and
new releases are out, the last one being 1.8.1.
BTW I wonder why the source package is built from the upstream binary
distribution tarball instead of the source one. The latter ships
jflex-maven-plugin which could be packaged as well.

Thanks,

_g.

[toc] | [next] | [standalone]

#11580

[Multipart message — attachments visible in raw view] — view raw

Hi,

Am 25.04.20 um 17:51 schrieb Gilles Filippini:
> Hi,
> 
> Is the jflex package still maintained? It has no upload since 2018 and
> new releases are out, the last one being 1.8.1.
> BTW I wonder why the source package is built from the upstream binary
> distribution tarball instead of the source one. The latter ships
> jflex-maven-plugin which could be packaged as well.
> 
> Thanks,
> 
> _g.

I am still active even if I don't currently make as many changes as I
did one or two years ago. I have added myself to uploaders back in 2016
because the package was unmaintained and we needed an update. JFlex
1.8.1 was only released two months ago. I usually hesitate to update
packages like jflex because we gain very little by doing so. This
package is mostly required for building packages. There is not really a
user visible exposure. As long as it works as expected, I believe we
don't need to update it more than once per release cycle, if at all.

I don't remember anymore how I build the package but from the rules and
control file I assume that we have to be very careful because jflex
build-depends on itself. It is a bit tricky to really build it from
scratch. Anyways if you want to make changes, please do so if it makes
Debian better. Don't forget to check the reverse-build-dependencies though.

Regards,

Markus

[toc] | [prev] | [next] | [standalone]

#11581

[Multipart message — attachments visible in raw view] — view raw

Markus Koschany a écrit le 25/04/2020 à 23:46 :
> Hi,
> 
> Am 25.04.20 um 17:51 schrieb Gilles Filippini:
>> Hi,
>>
>> Is the jflex package still maintained? It has no upload since 2018 and
>> new releases are out, the last one being 1.8.1.
>> BTW I wonder why the source package is built from the upstream binary
>> distribution tarball instead of the source one. The latter ships
>> jflex-maven-plugin which could be packaged as well.
>>
>> Thanks,
>>
>> _g.
> 
> I am still active even if I don't currently make as many changes as I
> did one or two years ago. I have added myself to uploaders back in 2016
> because the package was unmaintained and we needed an update. JFlex
> 1.8.1 was only released two months ago. I usually hesitate to update
> packages like jflex because we gain very little by doing so. This
> package is mostly required for building packages. There is not really a
> user visible exposure. As long as it works as expected, I believe we
> don't need to update it more than once per release cycle, if at all.
> 
> I don't remember anymore how I build the package but from the rules and
> control file I assume that we have to be very careful because jflex
> build-depends on itself. It is a bit tricky to really build it from
> scratch. Anyways if you want to make changes, please do so if it makes
> Debian better. Don't forget to check the reverse-build-dependencies though.

Thanks for these explanations. I'd like to have jflex-maven-plugin
packaged as well, but it implies building from the full source tarball
[1] which holds a few other subprojects. Not sure if it's worth the hassle.

[1] https://github.com/jflex-de/jflex/archive/v1.8.1.tar.gz

Best,

_g.

[toc] | [prev] | [next] | [standalone]

#11583

[Multipart message — attachments visible in raw view] — view raw

Am 26.04.20 um 01:02 schrieb Gilles Filippini:
[...]
> Thanks for these explanations. I'd like to have jflex-maven-plugin
> packaged as well, but it implies building from the full source tarball
> [1] which holds a few other subprojects. Not sure if it's worth the hassle.
> 
> [1] https://github.com/jflex-de/jflex/archive/v1.8.1.tar.gz

I'm not sure either. What is the intended use case for
jflex-maven-plugin? I had to package a similar package once,
gradle-jflex-plugin, but then upstream switched to another plugin.
Before I had to package yet another plugin, I decided to make some
modifications to make it compatible but I hope I don't need to touch it
again. So it depends on your goals, sometimes it is quite easy to
implement some sort of flex-plugin yourself. The plugin is often needed
to execute jflex on one or two files, well, of course you could also do
it manually in debian/rules. In any case you could file a wishlist bug
report, so the idea of packaging jflex-maven-plugin won't get lost.

Cheers,

Markus

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web