Re: problem with git-pull

I wrote yesterday: > El día martes, septiembre 12, 2023 a las 05:42:45p. m. +0200, Christoph > Moench-Tegeder escribió: > > > ## Matthias Apitz (g...@unixarea.de): > > > > > but when I now say 'git pull .' it says only: > > > > Drop the ".", because: > > 1. the first non-option to "git pull"

Re: problem with git-pull

Hi! > In short: Is there no way with git to pull only one special port > for a recompilation? For things like that I always have a git ports tree besides the poudriere ports tree. If I need one little recompile, I update the non-poudriere tree, take the one change from that tree that I need, put

Re: problem with git-pull

El día miércoles, septiembre 13, 2023 a las 12:55:20 +0200, Kurt Jaeger escribió: > Hi! > > > In short: Is there no way with git to pull only one special port > > for a recompilation? > > For things like that I always have a git ports tree besides the > poudriere ports tree. If I need one littl

Creating ports with utilisation of bsd.prog.mk

Hi, I would like to create two ports for software I have ported to FreeBSD. These two ports are classical 4.4BSD software that ship NetBSD and OpenBSD per default can could benefit FreeBSD users. The first one ist bsd-spell [1] and the other one is bsd-vacation [2]. The code it self is straigh

Re: Creating ports with utilisation of bsd.prog.mk

On Wed, Sep 13, 2023 at 03:42:14PM +0200, Gordon Bergling wrote: > Hi, > > I would like to create two ports for software I have ported to FreeBSD. > > These two ports are classical 4.4BSD software that ship NetBSD and OpenBSD > per default > can could benefit FreeBSD users. > > The first one is

Re: problem with git-pull

On Wed, 13 Sep 2023, Matthias Apitz wrote: El día miércoles, septiembre 13, 2023 a las 12:55:20 +0200, Kurt Jaeger escribió: Hi! In short: Is there no way with git to pull only one special port for a recompilation? For things like that I always have a git ports tree besides the poudriere

Re: problem with git-pull

Matthias Apitz writes: > I wrote yesterday: > >> El día martes, septiembre 12, 2023 a las 05:42:45p. m. +0200, Christoph >> Moench-Tegeder escribió: >> >> > ## Matthias Apitz (g...@unixarea.de): >> > >> > > but when I now say 'git pull .' it says only: >> > >> > Drop the ".", because: >> > 1.

Re: problem with git-pull

Martin Neubauer writes: > On Wed, 13 Sep 2023, Matthias Apitz wrote: > >> El día miércoles, septiembre 13, 2023 a las 12:55:20 +0200, Kurt Jaeger >> escribió: >> >>> Hi! >>> In short: Is there no way with git to pull only one special port for a recompilation? >>> >>> For things like th

Re: problem with git-pull

Hello. I think this is a very difficult problem for people like me who are just maintainers and do not have the right to commit. How are you all solving this? :) I have 3 clone repositories. 1. shallow clone created automatically by root using poudriere ports -c -m git+https. 2. full clone crea

Unmaintained FreeBSD ports which are out of date

Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this po

Wow: Building the likes of devel/llvm16 now requires building rust first (when rust is out of date). . .

Note: py39 is in use in my context. Building devel/llvm16 requires building textproc/py-recommonmark@py39 Building textproc/py-recommonmark@py39 requires building textproc/py-sphinx@py39 Building textproc/py-sphinx@py39requires building www/py-requests@py39 Building ww