Re: Lack of Flash support is no longer acceptable. Bounty established...

2008-06-20 Thread OutBackDingo
Believe it or not, there is useful content on the web in Flash :
 
 Google [Flash filetype:swf site:nasa.gov]
 (without the brackets).

There might be useful content, but that surely doesnt mean FreeBSD
itself as a desktop isnt usable, I think saying using firefox/flash for
flash based websites is difficult at best. but FreeBSD as a desktop is
plainly very usable

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [OT] Q: what would you choose for a VCS today

2008-02-01 Thread OutBackDingo
I dont think I follow why people think its that hard to convert the
FreeBSD src tree to some other RCS with history, branches and tags

I have a FULL CVS conversion to a mercurial tree converted from a
February 1, 2008 CVS snapshot. I also have a Full CVS converted to
Subversion. And they have been to the best of my determinations thru
ongoing testing fully converted. Id be more then happy to have others
double check the integrity of both trees and see if something got
missed. I seem to think this is doable. Seeing as Ive done it. And
honestly Mercurial just rocks. Id prefer to host it externally if
someone had some space, over all both trees consume space but not that
incredibly awful. Any takers for testing?


On Sat, 2008-02-02 at 00:34 +0200, Adrian Penisoara wrote:
 Hi,
 
 On Jan 31, 2008 6:02 PM, Mike Meyer [EMAIL PROTECTED] wrote:
 
  On Thu, 31 Jan 2008 08:45:55 +0200 Adrian Penisoara [EMAIL PROTECTED]
  wrote:
 Side-topic, if you bear with me: if you were to choose again what to
  use
   as source revision control system (VCS) from today's offerings, what
  would
   you choose to maintain FreeBSD's sources or a side-off project tracking
   FreeBSD as base that would allow better teams cooperation and easy code
   merging between projects/branches ?
 
  Pretty much any post-CVS VCS will do that. But if you want a good
  merge facility, Perforce's are - well, after getting used to them,
  everything else feels like throwing your code against the wall and
  hoping the right parts stick. I talked to one of the git developers
  about a year ago, and they were thinking about adding a guided merge
  inspired by what Perforce does.
 
 
 I do trust you on Perforce being a strong contender for the job, but,
 unfortunately, looking at their licensing terms for OSS projects I do get
 some second thoughts. Perhaps that's why FreeBSD did not migrate mainstream
 sources over to P4 yet ;)...
 
 Thanks,
 Adrian Penisoara
 ROFUG / EnterpriseBSD
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to [EMAIL PROTECTED]

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [OT] Q: what would you choose for a VCS today

2008-01-31 Thread OutBackDingo

 I'm having to use mercurial.
 I'm not really enjoying it.
 works ok for small projects. BSD is a bit big for it.
 doe work foe offline editing, but loses all your BSD history.
 
 probably SVK is the way to go from what I hear.

Im using mercurial on full FreeBSD trees, curiosity makes me ask where
do you the deficiency?

Ive had no issues patching, branching, merging, transplanting, tracking
vendor updates. The only issue i really had was a import of the full cvs
tree


___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: questions on development(7)

2007-11-14 Thread OutbackDingo

 I suppose you know about fromcvs.  I also guess you know that I suggest
 using git instead of hg.  Doesn't produce nasty large index files either :)
 
 cheers
   simon

So would you think cvs - git - hg might be easier to accomplish ??
Since one of my goals is to update projects Ive done based on FreeBSD
that require OS level updating

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: questions on development(7)

2007-11-13 Thread OutbackDingo
All ive seen in FreeBSD hg branches is a current and a releng_6
Id like to see a complete tree converted if there is one out there. I do
have some bandwidth to potentially host such a conversion for others.
question is does one exist ?

On Wed, 2007-11-14 at 17:48 +1030, Daniel O'Connor wrote:
 On Wed, 14 Nov 2007, Giorgos Keramidas wrote:
* Periodic 'imports' of the FreeBSD src/ tree as 'vendor' code
 
* Incremental conversion of /home/ncvs/src in 'changesets'
 
  I've been using a 'converted' tree for almost a year and a half now,
  to keep a local mirror of the src repository at `/ws/freebsd/head' on
  my laptop.  The first clean import of the current tree I am using was
  done during last summer:
 
 I have seen a few Hg repos although I haven't found one for RELENG_7 
 [yet].
 
 Also cvs20hg doesn't appear to grok Hg branches (probably because it 
 predates them) and it would be Really Nice(tm) if it did. (ENOCLUE is 
 my excuse for a lack of patches :)
 

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: questions on development(7)

2007-11-09 Thread OutbackDingo
well thats kinda hard to do with CVS, though other revision systems such
as mercurial, bazaar, git and perforce, even subversion do it well,
there is also a mercurial respository for FreeBSD out there some where

On Fri, 2007-11-09 at 05:36 +, Aryeh M. Friedman wrote:
 
  2. If yes to #1 how do I setup keeping everything except my modified
  code in sync (and if possible to retro activally apply patchs from the
  local branch unto the main source tree [/usr/src2])
 
  You won't be able to commit to the BSD repo from your server.  I
  think you should treat your repo as read only and use cvsup to keep
  it up to date.  At least that's what I do.
 
 What I meant was how do I keep from clobbering my local changes?
 

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: questions on development(7)

2007-11-09 Thread OutbackDingo

On Fri, 2007-11-09 at 14:43 +, Tom Evans wrote:
 On Fri, 2007-11-09 at 21:49 +0800, OutbackDingo wrote:
  well thats kinda hard to do with CVS, though other revision systems such
  as mercurial, bazaar, git and perforce, even subversion do it well,
  there is also a mercurial respository for FreeBSD out there some where
  
  On Fri, 2007-11-09 at 05:36 +, Aryeh M. Friedman wrote:
   
2. If yes to #1 how do I setup keeping everything except my modified
code in sync (and if possible to retro activally apply patchs from the
local branch unto the main source tree [/usr/src2])
   
You won't be able to commit to the BSD repo from your server.  I
think you should treat your repo as read only and use cvsup to keep
it up to date.  At least that's what I do.
   
   What I meant was how do I keep from clobbering my local changes?
   
  
 
 (Nothing like top posting to destroy the thread flow)
 
 OutbackDingo is incorrect. That is the entire purpose of CVS, otherwise
 they might as well call it VS..
 
 Your /usr/src will be a checkout of a particular branch of freebsd
 (called a working copy). You periodically update your cvs repository
 (where you checkout from) with the latest freebsd commits. 
 When you wish to, you update your working copy from your repository by
 issuing a 'cvs up'. This merges changes in the repository into your
 local copy, merging in with the local changes.
 When you want to see what has changed since you last did a 'cvs up',
 issue a 'cvs -n up'.
 When you want to see the local modifications in your working copy, issue
 a 'cvs diff'.
 
 Read the cvs red-bean book for more info.
 http://cvsbook.red-bean.com/cvsbook.html
 
 HTH
 
 Tom

Well I wouldnt say incorrect as i stated it was hard to do. Meaning its
easier to complete these tasks with a different RCS, in my OWN opinion.
So as not to clobber ones changes locally. I didnt say it could not be
done, its simply more difficult to achieve the same result as with other
RCS systems. The reason I sated as more difficult to do, Ive seen quite
a number of times when tracking a vendor branch, that merges had to be
more manually handled because of local changes. This is another of those
preferences people get into wars over, Best OS, Browser, RCS etc etc
etc... 

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]