Date: Sat, 1 Jul 2023 13:01:50 -0700 From: Patrick Mahan <plmahan@gmail.com> To: John Levine <johnl@iecc.com> Cc: freebsd-questions@freebsd.org, freebsd@gushi.org Subject: Re: Cannot install package dcc-dccd Message-ID: <CAFDHx1%2B4_DpEMM3woPheqt1rKeOpg1rMRsGG4-7pcPNPp4EZvw@mail.gmail.com> In-Reply-To: <20230701162653.2F70CFD36DFE@ary.qy> References: <4AE19679-7017-41F9-AB0B-77ECA1EB7603@gushi.org> <20230701162653.2F70CFD36DFE@ary.qy>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Jul 1, 2023 at 9:27 AM John Levine <johnl@iecc.com> wrote: > It appears that Dan Mahoney (Ports) <freebsd@gushi.org> said: > >-=-=-=-=-=- > > > >It would be cool, I suppose, if ports like this could install a “stub” > package that at least let you see the version in the ports > >tree, and could tell you when a new version was available to build. > > That would be horrible -- every time the package was updated, the real DCC > would go away > and all that would be left is the stub. > > Every system I've used has had a few ports I build from source because I > need something > other than the default config. I use pkg -l to keep the package system > from changing > them and look every once in a while to see if the port has changed. > > While I agree with you here about not having a port, I would like the description to be updated to state it requires a private build. If the package is listed as an available port, that, in my opinion, indicates it is available as a package. I realize that is a deficiency in my understanding of what the ports website entails, but since the clue as to why was in the makefile and not in the description, then I had to ask the group mind for help. Thanks, Patrick > R's, > John > > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr">On Sat, Jul 1, 2023 at 9:27 AM John Levine <<a href="mailto:johnl@iecc.com">johnl@iecc.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It appears that Dan Mahoney (Ports) <<a href="mailto:freebsd@gushi.org" target="_blank">freebsd@gushi.org</a>> said:<br> >-=-=-=-=-=-<br> ><br> >It would be cool, I suppose, if ports like this could install a “stub” package that at least let you see the version in the ports<br> >tree, and could tell you when a new version was available to build.<br> <br> That would be horrible -- every time the package was updated, the real DCC would go away<br> and all that would be left is the stub.<br> <br> Every system I've used has had a few ports I build from source because I need something<br> other than the default config. I use pkg -l to keep the package system from changing<br> them and look every once in a while to see if the port has changed.<br> <br></blockquote><div><br></div><div>While I agree with you here about not having a port, I would like the description to be updated to state it requires a private build. If the package is listed as an available port, that, in my opinion, indicates it is available as a package. I realize that is a deficiency in my understanding of what the ports website entails, but since the clue as to why was in the makefile and not in the description, then I had to ask the group mind for help.</div><div><br></div><div>Thanks,</div><div><br></div><div>Patrick</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> R's,<br> John<br> <br> </blockquote></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDHx1%2B4_DpEMM3woPheqt1rKeOpg1rMRsGG4-7pcPNPp4EZvw>