Re: RCS and $FreeBSD$ purge

On Fri, Jan 26, 2024, 7:32 PM Steve Kargl wrote: > I'm currently syncing src/lib/msun with my private libm > repository where I do much of my hacking on libm issues. > In looking at diffs, I see a few lingering RCS and > $FreeBSD$ tags. For example, lib/msun/amd64/s_scalbnl.

Re: RCS and $FreeBSD$ purge

Hi Steve, On Fri, Jan 26, 2024 at 06:32:26PM -0800, Steve Kargl wrote: > I'm currently syncing src/lib/msun with my private libm > repository where I do much of my hacking on libm issues. > In looking at diffs, I see a few lingering RCS and > $FreeBSD$ tags. For example, li

RCS and $FreeBSD$ purge

I'm currently syncing src/lib/msun with my private libm repository where I do much of my hacking on libm issues. In looking at diffs, I see a few lingering RCS and $FreeBSD$ tags. For example, lib/msun/amd64/s_scalbnl.S contains /* RCSID("$NetBSD: s_scalbnf.S,v 1.4 1999/01/02 05:15:40 kri

Re: i915: RCS timing out when being idled

On Sat, Dec 31, 2022 at 9:58 AM obiwac wrote: > Hey, > > I didn't find a more appropriate mailing list to post to, so here it goes: > I'm afraid I can't really help with your problem, but issues with graphics should be sent to FreeBSD graphics GitHub . I

i915: RCS timing out when being idled

. This isn't ideal though because the RCS ends up unhappy after a bit of load and the GPU hangs (RCS engine crashes) :P I guess the issues (the wedging and the hang) could be unrelated but I have a strong suspicion they are. I've been trying to understand how the whole i915 stuff is architectured

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Nov 06, 2016 at 12:09:30PM +0100, Eivind Nicolay Evensen wrote: > I also thought that perl was a good example of another piece of software > that once was provided and no longer is. Yes, that's true, but somewhat different. perl was removed because keeping it became incompatible with the

Re: [RFC] remove GNU rcs from FreeBSD 12

2016 2:27 AM, Eivind Nicolay Evensen wrote: > >> > >>> On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: > >>> > >>>> hi, > >>>> > >>>> For long we are planning to remove GNU rcs from base, after a fail

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sat, Nov 05, 2016 at 08:19:15PM -0500, Mark Linimon wrote: > On Thu, Nov 03, 2016 at 10:17:23AM +0800, Julian Elischer wrote: > > why should we remove it? > > IIUC the plan for several years has been to remove all GPLed software > from base. > > But in any case the conversation is moot. It

Re: [RFC] remove GNU rcs from FreeBSD 12

tiste Daroussin wrote: > >>>hi, > >>> > >>>For long we are planning to remove GNU rcs from base, after a failed > >>>attempt > >>>before FreeBSD 10.0. Let see where we are to be able to remove it from > >>>FreeBSD > >&g

Re: [RFC] remove GNU rcs from FreeBSD 12

On Thu, Nov 03, 2016 at 10:17:23AM +0800, Julian Elischer wrote: > why should we remove it? IIUC the plan for several years has been to remove all GPLed software from base. But in any case the conversation is moot. It was removed from head on 20161015 by bapt:

Re: [RFC] remove GNU rcs from FreeBSD 12

38:04PM +0200, Baptiste Daroussin wrote: >>> >>>> hi, >>>> >>>> For long we are planning to remove GNU rcs from base, after a failed >>>> attempt >>>> before FreeBSD 10.0. Let see where we are to be able to remove it from >>>> F

Re: [RFC] remove GNU rcs from FreeBSD 12

On Thu, 03 Nov 2016 03:17:23 +0100, Julian Elischer <jul...@freebsd.org> wrote: On 26/10/2016 2:27 AM, Eivind Nicolay Evensen wrote: On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: hi, For long we are planning to remove GNU rcs from base, after a failed attempt

Re: [RFC] remove GNU rcs from FreeBSD 12

to remove GNU rcs from base, after a failed attempt before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD 12. why should we remove it? What will replace it? it's an integral part of many people's systems. Is there a non gnu RCS with the same features? surprised to hear so

Re: [RFC] remove GNU rcs from FreeBSD 12

On 3/11/2016 10:45 AM, Pete Wright wrote: On 11/02/2016 19:17, Julian Elischer wrote: On 26/10/2016 2:27 AM, Eivind Nicolay Evensen wrote: On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: hi, For long we are planning to remove GNU rcs from base, after a failed attempt

Re: [RFC] remove GNU rcs from FreeBSD 12

On 11/02/2016 19:17, Julian Elischer wrote: On 26/10/2016 2:27 AM, Eivind Nicolay Evensen wrote: On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: hi, For long we are planning to remove GNU rcs from base, after a failed attempt before FreeBSD 10.0. Let see where we

Re: [RFC] remove GNU rcs from FreeBSD 12

On 26/10/2016 2:27 AM, Eivind Nicolay Evensen wrote: On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: hi, For long we are planning to remove GNU rcs from base, after a failed attempt before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD 12. why

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: > hi, > > For long we are planning to remove GNU rcs from base, after a failed attempt > before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD > 12. Whatever the outcome may be and

Re: [RFC] remove GNU rcs from FreeBSD 12

On 9/11/16 6:38 AM, Baptiste Daroussin wrote: hi, For long we are planning to remove GNU rcs from base, after a failed attempt before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD 12. GNU rcs is a GPLv2 software with newer version being GPLv3 preventing any updates

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Sep 11, 2016 at 10:17:26AM -0600, Warner Losh wrote: > On Sun, Sep 11, 2016 at 7:38 AM, Baptiste Daroussin <b...@freebsd.org> wrote: > > hi, > > > > For long we are planning to remove GNU rcs from base, after a failed attempt > > before FreeBSD 10.0

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Sep 11, 2016 at 7:38 AM, Baptiste Daroussin <b...@freebsd.org> wrote: > hi, > > For long we are planning to remove GNU rcs from base, after a failed attempt > before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD > 12. > > GNU rcs is

Re: [RFC] remove GNU rcs from FreeBSD 12

+1 to removing GNU RCS. FWIW; I did bring OpenRCS to the vendor area: https://svnweb.freebsd.org/base/vendor/OpenBSD/dist/usr.bin/rcs/ And I have a patch so that it builds on FreeBSD: https://people.freebsd.org/~pfg/patches/openrcs.diff It is known to NOT pass the GNU RCS testsuite and I

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: > ... > For long we are planning to remove GNU rcs from base, after a failed attempt > before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD > 12. > > GNU rcs is a GPLv2 software with n

Re: [RFC] remove GNU rcs from FreeBSD 12

On Sun, Sep 11, 2016 at 03:38:04PM +0200, Baptiste Daroussin wrote: > hi, > > For long we are planning to remove GNU rcs from base, after a failed attempt > before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD > 12. > > GNU rcs is a GPLv2 softwa

[RFC] remove GNU rcs from FreeBSD 12

hi, For long we are planning to remove GNU rcs from base, after a failed attempt before FreeBSD 10.0. Let see where we are to be able to remove it from FreeBSD 12. GNU rcs is a GPLv2 software with newer version being GPLv3 preventing any updates/fixes. From previous discussions there were

Re: What to do about RCS/OpenRCS

On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available. Of course, this would require people to learn something new, which

Re: What to do about RCS/OpenRCS

On May 11, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available

Re: What to do about RCS/OpenRCS

:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available. Of course, this would require people to learn something new, which I know can be a challenge. I

Re: What to do about RCS/OpenRCS

11, 2015 at 08:43:06AM -0700, Jos Backus wrote: On May 11, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many

Re: What to do about RCS/OpenRCS

, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available

Re: What to do about RCS/OpenRCS

On Mon, May 11, 2015 at 08:43:06AM -0700, Jos Backus wrote: On May 11, 2015 2:31 AM, Lars Engels lars.eng...@0x20.net wrote: On Sat, May 09, 2015 at 11:27:57AM -0700, Jos Backus wrote: Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too

Re: What to do about RCS/OpenRCS

On May 11, 2015 9:33 AM, David Chisnall thera...@freebsd.org wrote: [snip] And now you’re moving beyond missing the point and just trolling. Thanks for the ad hominen, David. You continue to make my point. Over and out, Jos David ___

Re: What to do about RCS/OpenRCS

is correct, and you are missing the point. Fossil, Git, Mercurial, and so on are all available as packages. No one is suggesting using RCS in preference to any of them. Deleting RCS from the base system would be nice, but unfortunately we can’t because of scripts that depend on some components

Re: What to do about RCS/OpenRCS

On 05/08/15 15:59, Davide Italiano wrote: On Fri, May 8, 2015 at 1:34 PM, Pedro Giffuni p...@freebsd.org wrote: Hi; I guess I see the following options: 1) Just leave GNU RCS in the tree. 2) Improve OpenRCS so it can be swapped in. 3) Remove RCS dependencies from other parts

Re: What to do about RCS/OpenRCS

On May 9, 2015, at 8:05 AM, Pedro Giffuni p...@freebsd.org wrote: We do that with GNU code anyways. The latest (GPLv3) version of RCS has already diverged and is incompatible for some third party software so we basically ran out of support from upstream. OpenRCS has it's own share

Re: What to do about RCS/OpenRCS

Maybe off-topic, but functionality-wise it might make much more sense to import Fossil. RCS has too many limitations this day and age when better tools are available. Of course, this would require people to learn something new, which I know can be a challenge. Jos

Re: What to do about RCS/OpenRCS

use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to disable GNU RCS and enable the new one I will happily twist up the new version and hammer on it. Yes, that's usually

Re: What to do about RCS/OpenRCS

On Thursday, May 07, 2015 04:18:38 PM NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should

Re: What to do about RCS/OpenRCS

On Fri, May 8, 2015 at 1:34 PM, Pedro Giffuni p...@freebsd.org wrote: Hi; I guess I see the following options: 1) Just leave GNU RCS in the tree. 2) Improve OpenRCS so it can be swapped in. 3) Remove RCS dependencies from other parts of the tree (e.g. etcupdate

What to do about RCS/OpenRCS

Hello; Some of you might recall that right before 10.0-Release there was a painful attempt to remove GNU RCS from the base system. From my point of view, the lessons learned from that were: -A lot more people than you might think find it useful to have a small version control system for thing

Re: What to do about RCS/OpenRCS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/07/15 12:09, Pedro Giffuni wrote: Hello; Some of you might recall that right before 10.0-Release there was a painful attempt to remove GNU RCS from the base system. From my point of view, the lessons learned from that were: -A lot

Re: What to do about RCS/OpenRCS

On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to disable GNU RCS and enable the new one I will happily

Re: What to do about RCS/OpenRCS

On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step

Re: What to do about RCS/OpenRCS

, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob to disable

Re: What to do about RCS/OpenRCS

On Thu, May 07, 2015 at 04:18:38PM -0700, NGie Cooper wrote: On Thu, May 7, 2015 at 1:38 PM, Pedro Giffuni p...@freebsd.org wrote: Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I

Re: What to do about RCS/OpenRCS

Hello; On 05/07/15 14:56, Lyndon Nerenberg wrote: On Thu, 7 May 2015, Pedro Giffuni wrote: Unfortunately I don't use RCS enough (it looks like I should though) so I am not in a good position to take the next step and deal with any fallout it may produce. If we can have a build-knob

Re: BE Loader Menu (was Re: rcs)

On 10/20/2013 20:58, Julian Elischer wrote: Kris. exactly what features need to be added to the boot process to allow what you want to do, but without using grub? Here's a list of the features we are using from grub: For install medium: * Hybrid DVD ISO/USB image in same file * BIOS / UEFI

Re: BE Loader Menu (was Re: rcs)

On Oct 21, 2013, at 6:32 AM, Kris Moore wrote: On 10/20/2013 20:58, Julian Elischer wrote: Kris. exactly what features need to be added to the boot process to allow what you want to do, but without using grub? Here's a list of the features we are using from grub: For install medium:

Re: BE Loader Menu (was Re: rcs)

Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I

Re: BE Loader Menu (was Re: rcs)

On Oct 10, 2013, at 9:42 AM, Julian Elischer wrote: On 10/11/13 12:39 AM, Teske, Devin wrote: On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can

Re: BE Loader Menu (was Re: rcs)

(didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic

Re: BE Loader Menu (was Re: rcs)

from Juergen Lock: If you mean it loads the kernel but then crashes instead of booting it then your grub2 version is missing this fix: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002 I used Super Grub2 Disk image on the System Rescue CD written to USB stick.

Re: rcs

On Thu, Oct 10, 2013 at 6:42 PM, Jakub Lach jakub_l...@mailplus.pl wrote: I have similar views. There is abundance of be-everything-for-everybody Linuxes and not enough lean and mean Unix-style kits... however did we neglect to realize that even some ports need rcs = clog-1.6.tar.gz

Re: rcs

neglect to realize that even some ports need rcs = clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog-1.6.tar.gz clog-1.6.tar.gz 100% of 17 kB 59 kBps

Re: rcs

Linuxes and not enough lean and mean Unix-style kits... however did we neglect to realize that even some ports need rcs = clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog

Re: rcs

On Tue, Oct 8, 2013 at 4:31 AM, Lyndon Nerenberg lyn...@orthanc.ca wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case. Still using RCS here and there, esp. managing /etc. Having

Re: BE Loader Menu (was Re: rcs)

realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic BE menus

Re: BE Loader Menu (was Re: rcs)

On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put

Re: rcs

a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case. Technically it is quite simple: I need RCS to start versioning config files, even before starting any customization. I know about several others who do the same

Re: rcs

On 10/11/13 12:34 AM, Jos Backus wrote: On Thu, Oct 10, 2013 at 9:10 AM, Julian Elischer jul...@freebsd.org mailto:jul...@freebsd.org wrote: On 10/9/13 11:59 PM, Jos Backus wrote: [snip] OK, but please, can we replace RCS with Fossil in 11 then? That adds a real

Re: BE Loader Menu (was Re: rcs)

On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing

Re: BE Loader Menu (was Re: rcs)

On 10/11/13 12:39 AM, Teske, Devin wrote: On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your

Re: rcs

On Thu, Oct 10, 2013 at 9:10 AM, Julian Elischer jul...@freebsd.org wrote: On 10/9/13 11:59 PM, Jos Backus wrote: [snip] OK, but please, can we replace RCS with Fossil in 11 then? That adds a real improvement to FreeBSD while giving people plenty of time to prepare. can fossil read rcs

Re: rcs

On Oct 10, 2013 9:38 AM, Julian Elischer jul...@freebsd.org wrote: On 10/11/13 12:34 AM, Jos Backus wrote: On Thu, Oct 10, 2013 at 9:10 AM, Julian Elischer jul...@freebsd.org wrote: On 10/9/13 11:59 PM, Jos Backus wrote: [snip] OK, but please, can we replace RCS with Fossil in 11

Re: rcs

... OK, but please, can we replace RCS with Fossil in 11 then? That adds a real improvement to FreeBSD while giving people plenty of time to prepare. Fossil was showing promise the last time I tried it. Quite frankly well since people expect RCS.. it is not a no brainer. you are asking

Re: rcs

On 10 October 2013 19:15, Jos Backus j...@catnook.com wrote: On Oct 10, 2013 9:38 AM, Julian Elischer jul...@freebsd.org wrote: [snip] well since people expect RCS.. it is not a no brainer. you are asking people to learn a whole new tool for functionality that is currently very

Re: rcs

On Oct 10, 2013 11:54 AM, Igor Mozolevsky i...@hybrid-lab.co.uk wrote: On 10 October 2013 19:15, Jos Backus j...@catnook.com wrote: On Oct 10, 2013 9:38 AM, Julian Elischer jul...@freebsd.org wrote: [snip] well since people expect RCS.. it is not a no brainer. you are asking people

Re: rcs

since people expect RCS.. it is not a no brainer. you are asking people to learn a whole new tool for functionality that is currently very simple.. edit file ci -l file add comment. Such is the price of progress. I envy people who don't have to learn anything new in order

Re: rcs

:38 AM, Julian Elischer jul...@freebsd.org wrote: [snip] well since people expect RCS.. it is not a no brainer. you are asking people to learn a whole new tool for functionality that is currently very simple.. edit file ci -l file add comment. Such is the price

Re: rcs

On Thu, Oct 10, 2013 at 8:51 PM, Diane Bruce d...@db.net wrote: ... OK, but please, can we replace RCS with Fossil in 11 then? That adds a real improvement to FreeBSD while giving people plenty of time to prepare. Fossil was showing promise the last time I tried it. Quite frankly

Re: rcs

On 2013-10-10, at 1:06 PM, Igor Mozolevsky i...@hybrid-lab.co.uk wrote: You're missing the point- the requirement is provide a way to keep track of changes for file X not have many fancy and unnecessary features... The point is to put back the specific RCS commands that were recently removed

Re: rcs

... The point is to put back the specific RCS commands that were recently removed. http://lists.freebsd.org/pipermail/svn-src-head/2013-October/052106.html Glen pgpwrgyRT0jiY.pgp Description: PGP signature

Re: rcs

... That may have been the requirement at the time of the RCS import but the world has changed in my view. Feel free to use the old tools though, nobody is saying you can't. Anyway, why not change this for 11? Do we feel RCS is superior simply because we are familiar with it? What about all the extra

Re: rcs

of changes for file X not have many fancy and unnecessary features... That may have been the requirement at the time of the RCS import but the world has changed in my view. Feel free to use the old tools though, nobody is saying you can't. Anyway, why not change this for 11? Do we feel RCS

Re: rcs

I have similar views. There is abundance of be-everything-for-everybody Linuxes and not enough lean and mean Unix-style kits... -- View this message in context: http://freebsd.1045724.n5.nabble.com/rcs-tp5850096p5850951.html Sent from the freebsd-current mailing list archive at Nabble.com

Re: rcs

On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case. Technically it is quite simple: I need RCS to start versioning config files, even before

Re: rcs

On Tue, Oct 8, 2013 at 11:34 PM, Lev Serebryakov l...@freebsd.org wrote: Hello, Daniel. You wrote 8 октября 2013 г., 19:40:23: DN If they get the package repositories back up - which I assume will DN happen before any official releases from 10 - it should just be pkg DN install rcs

Re: rcs

On 10/09/13 03:20, Hans Ottevanger wrote: On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case. Technically it is quite simple: I need RCS

Re: rcs

On Wed, Oct 9, 2013 at 2:03 PM, George Mitchell george+free...@m5p.com wrote: On 10/09/13 03:20, Hans Ottevanger wrote: On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up

Re: rcs

On 10/8/13 11:20 PM, Alfred Perlstein wrote: On 10/8/13 8:04 AM, sth...@nethelp.no wrote: I think the fact is that most direct users of RCS use it in a very simple way, and it works just fine for that. with no real need for any updates or any change. With all due respect Julian, The more we

Re: rcs

of things once they're moved from base to a package. A number of users and companies like that there is a very strict definition of base and that it wont change as the ports tree changes. Eg, you install 10.0 and get the rcs package from that. You then do an install of 10.0 a yeat later and install rcs

Re: rcs

On 10/9/13 2:35 AM, Freddie Cash wrote: On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein bri...@mu.org wrote: You're right on the money, to be honest this is one of the reasons why I've switched to using OSX as my desktop OS. zsh, vim, screen by default. and upgrades work. At the end of the

Re: rcs

- it should just be pkg DN install rcs. As challenges go, that doesn't seem too bad? Topic starter mentioned, that assumption that everybody has online connection is completely wrong! As far as I understand, it was his main objection -- they have a lot of offline computers at work (something related

Re: rcs

On 10/9/13 3:20 PM, Hans Ottevanger wrote: On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case. Technically it is quite simple: I need RCS

Re: [Heads Up] RCS removed from base

of us have RCS'd our /etc files, or have install scripts that use RCS it should be RCS.. I don't care WHICH RCS it is but it needs to be back in place by 10. and the easiest way of having it there in the mean while is jsut to revert the commit until the new one is ready

Re: rcs

- it should just be pkg DN install rcs. As challenges go, that doesn't seem too bad? Topic starter mentioned, that assumption that everybody has online connection is completely wrong! As far as I understand, it was his main objection -- they have a lot of offline computers at work (something related

Re: rcs

On Wed, Oct 09, 2013 at 07:17:11AM -0700, Alfred Perlstein wrote: Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That is broken now? memstick.img always had a minimal set of packages (mostly documentation

Re: rcs

Going off on a slight tangent... On Tue, 8 Oct 2013, Lyndon Nerenberg wrote: For this to work in a disconnected environment, you need a ports tree with a fully populated distfiles/ directory. The hack we came up with was to put a FreeBSD host on the external network, on which we ran a

Re: rcs

On 10/9/13 7:20 AM, Glen Barber wrote: On Wed, Oct 09, 2013 at 07:17:11AM -0700, Alfred Perlstein wrote: Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That is broken now? memstick.img always had a minimal set

Re: [Heads Up] RCS removed from base

On Tue, Oct 08, 2013 at 04:56:46PM -0400, Kurt Lidl wrote: On 10/8/13 4:33 PM, Cy Schubert wrote: In message 52542687.7000100 at pix.net, Kurt Lidl writes: On 10/8/13, Julian Elischer wrote: On 10/7/13 11:06 PM, Steve Kargl wrote: On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote:

Re: rcs

On Oct 9, 2013 5:39 AM, Kimmo Paasiala kpaas...@gmail.com wrote: On Wed, Oct 9, 2013 at 2:03 PM, George Mitchell george+free...@m5p.com wrote: On 10/09/13 03:20, Hans Ottevanger wrote: On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools

Re: rcs

On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer jul...@freebsd.org wrote: On 10/9/13 2:35 AM, Freddie Cash wrote: On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein bri...@mu.org wrote: You're right on the money, to be honest this is one of the reasons why I've switched to using OSX as my

Re: rcs

On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash fjwc...@gmail.com wrote: On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer jul...@freebsd.orgwrote: On 10/9/13 2:35 AM, Freddie Cash wrote: On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein bri...@mu.org wrote: You're right on the money, to be

Re: rcs

On 2013-10-09 12:23, Freddie Cash wrote: On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash fjwc...@gmail.com wrote: On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer jul...@freebsd.orgwrote: On 10/9/13 2:35 AM, Freddie Cash wrote: On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein bri...@mu.org

Re: rcs

On 10/09/13 15:47, Julian Elischer wrote: On 10/9/13 3:20 PM, Hans Ottevanger wrote: On 10/08/13 04:31, Lyndon Nerenberg wrote: Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their technical case

Re: rcs

On 10/09/2013 12:33, Allan Jude wrote: On 2013-10-09 12:23, Freddie Cash wrote: On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash fjwc...@gmail.com wrote: On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer jul...@freebsd.orgwrote: On 10/9/13 2:35 AM, Freddie Cash wrote: On Tue, Oct 8, 2013 at 9:09

Re: [Heads Up] RCS removed from base

... I notice in diff'ing your work vs my work, that I started with newer revisions of some of the files than the ones you have: I was well aware of that. There is no point doing much more until there is a decision from core. - Diane -- - d...@freebsd.org d...@db.net http://www.db.net/~db

BE Loader Menu (was Re: rcs)

menu with the ZFS datasets, I am not sure if the other issue can be resolved. I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years

Re: rcs

On 10/9/2013 3:17 PM, Alfred Perlstein wrote: Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That is broken now? At some point it was decided that the installer should be as simple as possible and package

Re: rcs

On 9 October 2013 11:28, Bruce Cran br...@cran.org.uk wrote: On 10/9/2013 3:17 PM, Alfred Perlstein wrote: Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That is broken now? At some point it was decided that

Re: rcs

On Oct 9, 2013, at 2:48 PM, Adrian Chadd wrote: On 9 October 2013 11:28, Bruce Cran br...@cran.org.uk wrote: On 10/9/2013 3:17 PM, Alfred Perlstein wrote: Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That

  1   2   3   >