Re: Updating the policy for conflicting binaries names ? [was: Re: Re: New package netgen-lvs with binary /usr/bin/netgen - already taken]
Philip Hands writes: > Paride Legovini writes: > >> Adam Borowski wrote on 14/09/2018: >>> On Thu, Sep 13, 2018 at 11:28:36PM +0200, Thomas Goirand wrote: > For example, in the Rust team, we have been discussing about packaging > fd (a find alternative developed using rust [1]). We are planning to > install it in /usr/bin/fd .. but this conflicts with something > completely different, fdclone a clone of fd, a MS-DOS file browser... fdclone isn't a shell utility, you just start it once, then you use its ncurse-like interface. Renaming it /usr/bin/fdclone wouldn't be a problem at all >>> >>> It _already_ is a symlink pair between "fd" and "fdsh". For the executable, >>> "fd" is the master, "fdsh" the slave, the man page prefers "fdsh". >> >> I am the prospect maintainer of fd-find; thanks for spotting this. I >> will ask the current maintainer of fdclone if he's willing to drop the >> 'fd' binary, keeping only 'fdsh' (upstream installs both as hard links). >> Shouldn't this be possible, I'll install the fd-find binary and man as: >> >> /usr/share/fd-find/bin/fd >> /usr/share/fd-find/man/man1/fd.1.gz >> >> and provide the convenience symlinks: >> >> /usr/bin/fdfind -> /usr/share/fd-find/bin/fd >> /usr/share/man/man1/fdfind.1.gz -> /usr/share/fd-find/man/man1/fd.1.gz >> >> Does this sound reasonable? > > It strikes me as rather presumptious to be trying to grab a new two > letter command at this point in the history of *nix (particularly when > it is already in use). > > Personally, I'll never willingly install a binary named that, because it > seems very likely to tickle my dyslexia. I'd expect it to make me very > grumpy if I ever have to maintain a script that includes references to > both df and fd nearby one another. Ignore the above -- I managed to misread what you asked as dropping 'fd' into /usr/bin, which is the oposite of what you were actually asking. Sorry if I introduced any aditional confusion. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Limiting the size of installed changelogs
On Fri, 14 Sep 2018 at 23:59, Raphael Hertzog wrote: > On Fri, 14 Sep 2018, Marc Haber wrote: > > Has anybody gotten dpkg path-exclude to work? > > Yes. It's been a long time that I have not used it but the main problem > is that to be effective the option must be used right from the start (i.e. > already at the debootstrap stage) otherwise you have to manually cleanup > the excluded files (at the time when you put the option in dpkg's > configuration file). > > (I don't remember if reinstalling all the packaes achieves the desired > result too) > It does. Cheers, mwh
Bug#908885: ITP: ring-kde -- Qt based client for the Ring daemon.
Package: wnpp Severity: wishlist Owner: Scarlett Gately Moore * Package name: ring-kde Version : 3.0.0 Upstream Author : BlueSystems GmbH * URL : https://download.kde.org/stable/ring-kde/ * License : LGPL-2.1+, GPL-3+, GPL 3, GPL-2+ Programming Lang: C++ Description : Qt based client for the Ring daemon. Ring is a free and universal communication platform which preserves the users' privacy and freedoms. . * A telephone: a simple tool to connect, communicate and share. * A teleconferencing tool: easily join calls to create conferences with multiple participants. * A media sharing tool: Ring supports a variety of video input options, including mutliple cameras and image and video files, and the selection of audio inputs and outputs; all this is supported by multiple high quality audio and video codecs. * A messenger: send text messeges during calls or out of calls (as long as your peer is connected). * A building block for your IoT project: re-use the universal communications technology of Ring with its portable library on your system of choice. I plan on maintaining this.
dpkg path-exclude (was: Limiting the size of installed changelogs)
On Sat, 15 Sep 2018 22:31:42 +1200, Michael Hudson-Doyle wrote: >On Fri, 14 Sep 2018 at 23:59, Raphael Hertzog wrote: > >> On Fri, 14 Sep 2018, Marc Haber wrote: >> > Has anybody gotten dpkg path-exclude to work? >> >> Yes. It's been a long time that I have not used it but the main problem >> is that to be effective the option must be used right from the start (i.e. >> already at the debootstrap stage) otherwise you have to manually cleanup >> the excluded files (at the time when you put the option in dpkg's >> configuration file). >> >> (I don't remember if reinstalling all the packaes achieves the desired >> result too) >> > >It does. Can you share some command lines and/or scripts and/or configuration files please? Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Bug#908894: ITP: lazygit -- Simple terminal UI for git commands
Package: wnpp Severity: wishlist Owner: Jongmin Kim X-Debbugs-CC: debian-devel@lists.debian.org, team+pkg...@tracker.debian.org * Package name: lazygit Version : 0.2.1 Upstream Author : Jesse Duffield * URL : https://github.com/jesseduffield/lazygit * License : Expat Programming Lang: Go Description : Simple terminal UI for git commands lazygit is a simple terminal UI for git commands that makes git easy to use. All features of lazygit can be easily used by using the directional keys and simple keystrokes of the keyboard. . lazygit provides the following git features with cool interface: * Adding files easily * Resolving merge conflicts * Easily check out recent branches * Scroll through logs/diffs of branches/commits/stash * Quick push/pull * Squash down and rename commits lazygit is an easy-to-use git terminal UI for wrapping a bunch of git commands. It also provides visualising the branches which have difficult and complex relationships.
Re: dpkg path-exclude (was: Limiting the size of installed changelogs)
On Sun, 16 Sep 2018 at 01:42, Marc Haber
wrote:
> On Sat, 15 Sep 2018 22:31:42 +1200, Michael Hudson-Doyle
> wrote:
> >On Fri, 14 Sep 2018 at 23:59, Raphael Hertzog wrote:
> >
> >> On Fri, 14 Sep 2018, Marc Haber wrote:
> >> > Has anybody gotten dpkg path-exclude to work?
> >>
> >> Yes. It's been a long time that I have not used it but the main problem
> >> is that to be effective the option must be used right from the start
> (i.e.
> >> already at the debootstrap stage) otherwise you have to manually cleanup
> >> the excluded files (at the time when you put the option in dpkg's
> >> configuration file).
> >>
> >> (I don't remember if reinstalling all the packaes achieves the desired
> >> result too)
> >>
> >
> >It does.
>
> Can you share some command lines and/or scripts and/or configuration
> files please?
>
Ubuntu's minimal images run something like
chroot chroot dpkg-query -f '${binary:Package}\n' -W | chroot chroot xargs
apt-get install --reinstall
after running deboostrap and setting up the includes. The gory details are
around here:
https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/bionic-proposed/view/head:/live-build/auto/build#L100
Cheers,
mwh
