On 9/11/2012 00:24, Jelle Hermsen wrote:
Hiya,
Combining Chris' patches with mine seemed to fix Racket 5.3. I still
have to do some thorough testing to see if everything works as it
should. You can get the latest version here:
www.jellehermsen.nl/jel/racket-5.3.tar.gz
Hi Jelle,
I added some
On 9/15/2012 19:54, Chris Turner wrote:
On 09/15/12 09:09, John Marino wrote:
Hi Jelle,
I added some minor modifications to your patches and committed them to
pkgsrc head.
Thanks for the hard work you and Chris did in getting both versions
of Racket to build on DragonFly!
awesome thanks
I've used my time without internet to work on getting GCC 4.7.1 into
base. After putting in a few hours each day over several weeks, I've
gotten gcc 4.7.1 with Link-Time-Optimization building cleanly with make
buildworld. I still need to buildworld with gcc 4.7 and verify
everything works
On 9/25/2012 14:05, Pierre Abbat wrote:
Will the packages build better with 4.4 or 4.7?
Pierre
Unknown at this time, but there was significant regression in packages
after moving to gcc 4.4. I don't expect much regression with 4.7
because NetBSD uses 4.5 and SunOS and Linux use 4.6 and
On 9/25/2012 17:10, Pierre Abbat wrote:
On Tuesday, September 25, 2012 14:34:20 John Marino wrote:
Unknown at this time, but there was significant regression in packages
after moving to gcc 4.4. I don't expect much regression with 4.7
because NetBSD uses 4.5 and SunOS and Linux use 4.6
There was a bootstrapping issue with the new GCC 4.7 that caused a
broken world build for the vast majority of users. As of commit
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/ce38cc158226ab53f412af0f540e6a2e9d53b70f
(Wed, 3 Oct 2012 08:33:48 + (10:33 +0200)) this problem was
This is my first pass at building packages with the new base compiler
in DragonFly 3.2, gcc 4.7.2. Due to ongoing i386 panics, I upgraded the
kernel in the middle of the run and that caused some artificial breakage,
most obviously with devel/p5-perl-headers.
There are other perl failures here,
On 10/15/2012 16:33, B. Estrade wrote:
On Mon, Oct 15, 2012 at 03:17:08PM +0100, peeter (must) wrote:
On Mon, Oct 15, 2012 at 2:39 PM, B. Estradeestr...@gmail.com wrote:
Just throwing this out there, but one thing that made me sad about
FreeBSD's dumping GCC as base was that it was also
On 10/22/2012 21:04, Mehmet Erol Sanliturk wrote:
Dear All ,
In
http://mirror-master.dragonflybsd.org/packages/x86_64/DragonFly-3.1/pkgsrc-2012Q2/All/
there is a package kde-3.5.10.tgz :
http://mirror-master.dragonflybsd.org/packages/x86_64/DragonFly-3.1/pkgsrc-2012Q2/All/kde-3.5.10.tgz
It seems
On 11/4/2012 00:40, Edward M wrote:
Can not upgrade from DragonFly 3.0.3.1 to 3.2.1
i executed:
cd /usr/src/
git branch DragonFly_RELEASE_3_2
git checkout DragonFly_RELEASE_3_2
after the last command, appears nothing gets downloaded.
anyway, i continued with the rest of the commands, maybe i
Original Message
The following report is used the alternate compiler in DragonFly, gcc 4.7.2.
The first run was started on Nov 21. Several packages were fixed and it was
rerun without otherwise updating the repository.
It is compared with another gcc 4.7.2 run from Oct 13.
On 12/12/2012 23:04, John Marino wrote:
I just added a DragonFly-specific directive to the master branch of
pkgsrc, DRAGONFLY_CCVER.
If you put DRAGONFLY_CCVER=gcc47 in the /usr/pkg/etc/make.conf file,
it will build all packages with DragonFly's alternate compiler, gcc
4.7.2. Alternatively, you
On 1/3/2013 03:56, Justin Sherrill wrote:
On Wed, Jan 2, 2013 at 7:46 PM, John Marino dragonfly...@marino.st
mailto:dragonfly...@marino.st wrote:
The long-term plan is that building from source will *not* be
recommended to new users. Since theoretically every single port
On 1/4/2013 04:44, Justin Sherrill wrote:
I'm thinking about pkgsrc bulk builds in comparison, because we already
have pkgsrc building machines and binary download locations that could
also support DPorts.
If I read your example right, there wouldn't be a DragonFly 3.4 (Latest)
- once 3.6 is
This is just a quick note about some progress François and I have made
in the last couple of days:
1) There are more than 17,000 dports now
2) Libreoffice 3.6 has been added
3) 107 Libreoffice language packs have been added, so you can have LO in
your native language
4) XFce4 4.10 has been
On 1/16/2013 20:12, John Marino wrote:
I just updated a 17-year tool, flex, the master branch. It's a bootstrap
tool. I think quickworld will still work, but I only tested the full
buildworld. If you see any strange build errors involving lex, you
probably want to do a full buildworld
On 1/17/2013 00:03, John Marino wrote:
On 1/16/2013 23:05, John Marino wrote:
On 1/16/2013 20:12, John Marino wrote:
I just updated a 17-year tool, flex, the master branch. It's a bootstrap
tool. I think quickworld will still work, but I only tested the full
buildworld. If you see any strange
The update of M4, flex, and byacc together (all bootstrap tools) has
made it challenging to build HEAD from previous release branches and
those on the dev branch 3.3 that are set prior to the M4 import.
The following procedure *should* work for everyone that wishes to build
the latest world:
The gcc-4.4 compiler is still the default compiler on DragonFly-3.3.
There seems to be general consensus on IRC that it's time to promote
gcc-4.7 to that role and have gcc-4.4 serve as the backup.
Is there any major objection to doing this?
From a pkgsrc point of view, over 11,150 packages
On 2/1/2013 16:28, Loïc BLOT wrote:
Hello,
I'm a CNRS apprentice on system, network and security engineering.
Loic Blot
Le 1 févr. 2013 à 16:12, Sdävtakersdavta...@gmail.com a écrit :
Hi,
I just started working here and wondering if anyone else is already here.
Damian
I had been working
So
1) They are broken permanently until A) somebody patches them or B)
somebody updates the package which has a good chance of working with gcc47
2) They aren't broken if you use DRAGONFLY_CCVER=gcc44 which we have
done in the pkg themselves for those pkgs hopelessly broken on gcc4.7.
The ones
works for me.
On 2/2/2013 22:42, Edward M wrote:
Hi,
Am I the only one that can not access drgaonflyBSD.org or is the website
down?
On 2/5/2013 19:42, Samuel J. Greear wrote:
On Fri, Feb 1, 2013 at 2:03 AM, John Marinodragonfly...@marino.st wrote:
The gcc-4.4 compiler is still the default compiler on DragonFly-3.3. There
seems to be general consensus on IRC that it's time to promote gcc-4.7 to
that role and have gcc-4.4
On 2/10/2013 08:34, Pierre Abbat wrote:
I'm doing a rolling-replace on DragonFly, using 2012Q4, and I get this:
CCLD utilities/compare
CCLD utilities/composite
/usr/obj/pkgsrc/graphics/ImageMagick/work/.buildlink/lib/libIlmImf.so:
undefined reference to
On 2/10/2013 17:31, Pierre Abbat wrote:
On Sunday, February 10, 2013 10:15:43 John Marino wrote:
Are you using 3.3-master here, post-gcc-4.7 default?
If so, you might be mixing gcc-4.4 and gcc-4.7 built packages. If you
have 4.4 packages it's probably best to put DRAGONFLY_CCVER?=gcc44 in
/usr
On 2/12/2013 18:46, Matthew Dillon wrote:
So I would propose that the world-backup mechanic be a manual target
and not an automatic process. e.g. like:
make backupworld
make restoreworld
I do not think it would be a good idea to automatically backup the world
On 2/21/2013 23:22, Roger Lawhorn wrote:
Hello,
Hi Roger,
I am new to dragonfly bsd. Fear not, I am a unix (and microsoft) admin and a
programmer from the 80's. Nowadays I just do unix batch, perl, and xsl. You
don't need to teach me much.
I am using vmware player 5. 64bit will not
On 2/25/2013 00:44, r...@insightbb.com wrote:
Thankyou for the repsonse.
I just did the upgrade process and what I see after a reboot is:
After upgrading I am at v3.2.2.29.gaaef-RELEASE #0
It appears that all you did was upgrade to the latest 3.2.
Use git branch to in /usr/src directory to
On 3/30/2013 06:16, vasily postnicov wrote:
Hello! I started porting SBCL to DragonFlyBSD. Previous (and only)
attempt was
http://leaf.dragonflybsd.org/mailarchive/users/2006-05/msg00108.html as
far as I know. Google gives no more info on sbcl on dragonfly except
this link.
So I forked
On 4/1/2013 10:41, Constantine Aleksandrovich Murenin wrote:
As an IPv6-only site, we hereby declare that 2013-04-04 is an IPv4 day.
On April 4, we will temporarily enable IPv4 connectivity, for one day,
to test the water. (We've heard that IPv4 has some connectivity issues
related to NAT,
On 4/15/2013 16:43, Vitaly Shevtsov wrote:
Hello!
I've decided to try dports. I successfully compiled xorg-server and
fluxbox. The I typed fluxbox -info and saw this:
Fluxbox version: 1.3.5
...
Compiler: GCC
Compiler version: 4.4.7 2012.03.13.
So my question is why gcc 4.4.7 was used to
On 5/6/2013 14:52, Petr Janda wrote:
Now, the _very_ interesting (and unexpected) part is the less than 2% pkgsrc
packages usage.
Maybe it's just that pkgng is so much better, maybe it's that pkgsrc users
prefer to build software from source. Difficult to know.
In any case, I don't see a reason
On 5/6/2013 15:20, John Marino wrote:
On 5/6/2013 14:52, Petr Janda wrote:
Now, the _very_ interesting (and unexpected) part is the less than 2%
pkgsrc
packages usage.
Maybe it's just that pkgng is so much better, maybe it's that pkgsrc
users
prefer to build software from source. Difficult
On 5/6/2013 18:58, Freddie Cash wrote:
Clang is the default compiler for FreeBSD 10, and pkgng is the default
package management tool as well. Thus, all packages for FreeBSD 10 are
built using Clang, in pkgng format.
No, not thus.
Clang is the compiler for base and world. There's no
On 5/7/2013 22:55, Volodymyr Kostyrko wrote:
Less then 5% actually. I'm running my desktop with 567 installed
packages of which only 10 really require GCC to build (cd /usr/ports;
pkg query %o | sed 's|$|/Makefile|' | xargs -n1 grep -H USE_GCC | wc
-l). I have extra 6 overrides in configuration
On 5/8/2013 14:16, Antonio Olivares wrote:
I am unfamiliar with pkgsrc as to update the tree, in FreeBSD, we use
portsnap fetch * to update the tree, but here I am kind of lost. I
know that there exits dport but I prefer the ports tree structure so I
want to use pkgsrc but if there is an idiot
On 5/9/2013 22:34, Antonio Olivares wrote:
I am now confused. I see that there is pkg, which is like pkg_add,
pkg_delete, ..., in old FreeBSD now they have pkgng and the old tried
and true FreeBSD ports. The dports is now in DragonFlyBSD making use
of the FreeBSD ports pkgng stuff to install
This might be handled by xorg.
Look at /etc/X11/xorg.conf, section InputDevice
Is there a mouse section there (Probably identified as Mouse0).
You might want to paste that. Mine has Device defined as /dev/sysmouse.
JustinS told you that before, and he also wrote the following on this
very
On 5/13/2013 19:32, Antonio Olivares wrote:
is the iced-tea-web package available from dports?
I check in /usr/dports/java/ but it is not present there. I would
like to have the iced-tea-plugin to run java apps. I have installed
openjdk package:
openjdk-7.9.05_2 Java Development
A month ago, the i386 dports packages were uploaded to the appropriate
RELEASE directory, and the LATEST directory was simply a copy of it.
Today I finished uploading 10,700+ packages which are rebuilds,
replacements and new packages to the LATEST directory. There are 19,926
packages in this
On 5/20/2013 14:44, Loïc BLOT wrote:
Hi all,
today i would like to test postgresql with dports. Unfortunately, It's
impossible to compile postgresqlXX-server (all versions).
The port compile says:
pq.5 not found
By searching where is the problem, i have noticed that the library comes
with
On 5/20/2013 16:25, Loïc BLOT wrote:
Hello John
it's a fresh DragonFly 3.4.1 install, and i have purged /usr/pkg as you
expect.
I build from source because i prefer custom compile
options/optimizations, like i do in all my FreeBSD systems :)
postgresql91-client doesn't get gettext dependancy
On 5/16/2013 04:48, Chris Turner wrote:
... and while I'm at it - this [Bug#2561] + Bug#2133, etc.
seem like excellent examples of the 'why keeping =2 platforms going is
a good idea'
argument.
/soapbox
I need to first point out that nobody is saying there are not benefits
to having multiple
On 5/24/2013 13:17, Gavin Reade wrote:
Anyway enough babble, I had DFly 3.2 and upgraded to 3.4, lost my
X server config, machine went dead (no virtual consoles) so I just
installed a vanilla 3.4.
If you had an x86-64, it may have been the avx support that kill your
packages. They all have
There are DragonFly-only dports, and in a few cases there are dports
that used to be in FreeBSD but have since been deleted. Normally I
purge these dports soon after, although occasionally I keep them (e.g.
libusb v0.1 which is needed for legacy usb support). I've already
purged a couple of
On 6/1/2013 19:34, Francois Tigeot wrote:
Another issue: kde4 applications don't install their binaries in
/usr/local/bin but /usr/local/kde4/bin.
The default PATH will need to be changed.
Why is that an issue?
To me it's a good thing, and obviously FreeBSD intentionally did this.
When
On 6/1/2013 02:11, Petr Janda wrote:
Keep it until it breaks. If the fix is minor keep it a bit longer, but
if it will take substantial time to fix, purge it.
Just an idea.
But there are two keep options.
2) only KDE3
3) everything needing QT3 including KDE3
So which keep option did you
On 6/2/2013 13:39, Francois Tigeot wrote:
On Sun, Jun 02, 2013 at 01:28:56PM +0200, John Marino wrote:
On 6/1/2013 19:34, Francois Tigeot wrote:
Another issue: kde4 applications don't install their binaries in
/usr/local/bin but /usr/local/kde4/bin.
The default PATH will need to be changed
On 6/1/2013 13:13, Chris Turner wrote:
On 05/30/13 01:59, Francois Tigeot wrote:
The pkgsrc trend is reinforced though, almost nobody downloads pkgsrc
packages.
This could be an indication that pkgsrc users are more likely
to build from source
Since Francois is saying that pre-building
As I have previously mentioned, only ports that can be built on x86_64
are eligible for dports. This eliminates i386-only ports in the FreeBSD
ports collection.
So there won't be any pre-built binaries, but if one is desperate for
some of these i386-only ports, there may be a way. I have
On 6/3/2013 14:48, Jeremy C. Reed wrote:
On Sun, 2 Jun 2013, John Marino wrote:
Except you can't mix these systems.
This is misleading. If pkgsrc does not work when dports is used, then it
is a bug and should be fixed. Pkgsrc is designed to work when other
software is installed.
I've been
On 6/3/2013 23:20, Tim Darby wrote:
Apologies if this has already been covered but, if I don't see a binary
at this point, does that mean it couldn't be built? For example, I see
a binary for libtorrent, but not rtorrent. Is there a place to go to
see a status report of the dports builds?
In
On 6/6/2013 14:54, Gavin Reade wrote:
Well here is a tricky one - i'm running i386 DFly 3.4 on a P4 (i586) -
as reported by dmesg. Sysinfo reports an i386 proceesor, but I am using
dports right from the beginning of the install. I've had no trouble
installing dports on this machine (not that
On 6/7/2013 07:43, Gavin Reade wrote:
Thanks for that John,
You're absolutely right, I competely missed your point! Anyway I
tried building ghc form dports - it works after a fashion but there was
no ghci (took days and days as well :-)), so I tried your recipe. I got
the following error
On 6/8/2013 11:59, Andrey N. Oktyabrski wrote:
On 17.05.2013 14:32, Andrey N. Oktyabrski wrote:
I have a problem with DragonFly v3.4.1.5.g6a92f on kvm virtual machine.
It hangs after some time after boot. Without panic and crashdump.
DragonFly v3.4.1.2.g0622d on another kvm works fine.
Both
On 7/23/2013 16:36, Justin Sherrill wrote:
How will people know to install that library?
On Mon, Jul 22, 2013 at 6:13 PM, Francois Tigeot ftig...@wolfpond.org wrote:
On Mon, Jul 22, 2013 at 07:10:06PM +0200, Max Herrgård wrote:
Den 2013-07-21 15:33:16 skrev Francois Tigeot
On 7/25/2013 05:55, Justin Sherrill wrote:
On Wed, Jul 24, 2013 at 2:01 AM, John Marino dragonfly...@marino.st wrote:
For example, yesterday textproc/rasqal broke on dports
because of a curl update. Had curl been pushed as soon as it built, it
would have broken basically everything KDE4
On 7/25/2013 15:06, Justin Sherrill wrote:
If there's packages that build correctly and have no dependencies on
any failing package, why not update them? Is it because the rsync is
set to clear out unmatched packages at the destination, or is there
another reason?
Flip the question.
What is
On 8/26/2013 17:49, Luca Ferrari wrote:
If I remember right, SMF not only does a controlled startup of a
service, but also a controlled shutdown, that is something that seems
to me lacks in rc. In other words, once the network is going down,
also all daemons that rely on the network are, and
On 8/27/2013 00:09, Freddie Cash wrote:
So, by looking at the LibreOffice codebase, you're looking at:
- original, ancient StarOffice code
- Sun Microsystem's updated OpenOffice.org code
- Oracle OpenOffice.org code
- Apache OpenOffice.org code (maybe)
- LibreOffice code
Not
On 8/27/2013 13:20, Petr Janda wrote:
Personally, I think smf manifests being in XML(i dislike) may be a
problem with many users who
are not used to reading and writing XML files.
That's one of the things I hated on SMF!
But I guess the configuration can be easily translated from
On 9/9/2013 18:40, joris dedieu wrote:
- controlled shutdown
- restart
- dependancy map
- parallelism
could easily be tacked on to rcng with a bit of ingenuity, and probably by
using
simple shell conventions or minor tweaks to 'rcorder'/'rc.subr', etc. rather
than strict / annoying /
On 9/9/2013 23:57, Tobias Weingartner wrote:
It uses XML, which is bad because I don't understand it is a very
reasonable argument. Especially if a significant portion of your
customers/users say the same thing...
You're talking generically, which is fine.
However, this is a specific case
On 9/10/2013 00:13, Outback Dingo wrote:
i still believe launchd easier and the best solution
Nobody until today was talking about launchd
You don't define easier.
What is easier? Easier to port from Linux? Easier for a sysadmin to
run? Did anyone do a scientific study? If you were a lawyer
On 9/10/2013 00:31, Outback Dingo wrote:
actually i mentiioned it weeks ago... easier to integrate,
Integrate into the BSD codebase? Where is the analysis to prove that
assertion?
easier to manage,
Easier than what? Is there a survey or analysis to support that it is
easier than
On 9/10/2013 07:39, james wrote:
On 09/09/2013 23:21, John Marino wrote:
5) XML is parsed faster than YAML or JSON. It's superior that way.
Maybe we are talking milliseconds here but...
Since when was XML parsed faster than JSON?
Compliant XML parsing has a whole lot of complexity
On 9/10/2013 09:30, joris dedieu wrote:
expressiveness is IMHO the first need of a boot process. You tell the
machine the way you want it to start. For me SMF does not answer this.
Shell does.
I think we just got down to the crux of this.
You're talking about boot process, how you want things
On 9/10/2013 13:54, joris dedieu wrote:
2013/9/10 Petr Janda elekktrett...@exemail.com.au:
Have a look at the manifests, vast majority of them don't need shell
scripting.
I disagree this point.
Here a basic OpenIndiana distribution (SunOS blandine1 5.11 oi_151a7
i86pc i386 i86pc Solaris)
I would have preferred not to respond to any of this, but ...
On 9/10/2013 17:35, Dmitrij D. Czarkoff wrote:
Put otherwise: I can do quite a lot of things using awk alone. What can I do
with XML alone?
You are comparing a data format to an program. This question doesn't
merit a response.
Hi all,
Sometime tonight, I'm going to merge the dports staged branch with
master. It's not as good a qualify as previous merges because neither
gnustep nor libreoffice built, despite the latter having no changes.
The FreeBSD ports collection has (without explicitly stating it) made a
policy
On 9/22/2013 05:47, Pierre Abbat wrote:
On Saturday, September 21, 2013 08:30:35 Alex Hornung wrote:
Our gdb doesn't support our thread implementation (libthread_xu), so you
can't debug multithreaded userland processes.
What other operating systems use libthread_xu? Is there any way to fix
On 9/22/2013 12:45, Pierre Abbat wrote:
On Sunday, September 22, 2013 08:37:15 John Marino wrote:
On 9/22/2013 05:47, Pierre Abbat wrote:
On Saturday, September 21, 2013 08:30:35 Alex Hornung wrote:
Our gdb doesn't support our thread implementation (libthread_xu), so you
can't debug
The libiconv update ended up requiring a major update to libc, including
strings and stdtime. Additionally, locales/ctype handling had to be
updated as well as all of these things are interdependent. The patch
involves 831 files and is 3.6M in size. I'd like to thank Joris for
reviewing the
On 10/9/2013 22:43, Matthew Dillon wrote:
As of the next release we will be officially moving to dports.
It's already the default on master and will become the only
option on the next release.
Our copy of the pkgsrc repo is now frozen. Well, actually it kinda
froze
On 11/7/2013 07:25, Andrey Oktyabrskiy wrote:
Good day.
I try to use dports and have strange error: [snip]
install -m 755 git-subtree /usr/local/libexec/git-core
asciidoc -b docbook -d manpage -f ../../Documentation/asciidoc.conf \
-agit_version=1.8.4.1 git-subtree.txt
asciidoc:
On 11/7/2013 09:24, Andrey Oktyabrskiy wrote:
On 07.11.2013 11:46, John Marino wrote:
Are you using pkg-1.1.4_8 ?
(check with pkg info pkg)
$ pkg info pkg
pkg-1.1.4_1
If it's not that version, go to /usr/dports/ports-mgmt/pkg and:
make clean
make deinstall
make install clean
Does
On 11/7/2013 11:18, Andrey Oktyabrskiy wrote:
Good day.
I need a cyrus-imapd, but it is absent in dports. Why?
The answer is the same for every missing port. If it doesn't build on
DragonFly, it doesn't exist in dports. On x86-64, every port should be
buildable.
That said, the error looks
On 11/7/2013 11:28, John Marino wrote:
On 11/7/2013 11:18, Andrey Oktyabrskiy wrote:
Good day.
I need a cyrus-imapd, but it is absent in dports. Why?
The answer is the same for every missing port. If it doesn't build on
DragonFly, it doesn't exist in dports. On x86-64, every port should
On 11/9/2013 14:41, Muhammad Nuzaihan Bin Kamal Luddin wrote:
Oh well, i will use vkernels in the Virtualized DragonFlyBSD anyway if i
can get it to work.
DragonFly does work in KVM, but you may have to be patient to wait for
somebody familiar with running DF in KVM to give you some pointers.
I have just updated the dports package set for Release 3.4.x for i386
platform. The 3.6.1 Release packages for i386 were already in place.
As of right now, the package situation on i386 is the best that it can
possibly be.
However, I am washing my hands of i386 and I won't contribute to it
Another thing I've been hoping (in vain) for the project to produce is a
real road map showing what features are intended for which release.
Since such a document does not exist and probably will not exist, I
though I'd start of list of things that I think we should try to
accomplish on the 3.7
On 11/21/2013 12:12, Alex wrote:
Thank you for this roadmap. As a newcomer wanting to contribute, it
really helps with an overview of what could be done.
I'll give a try on the bmake update if that's OK :)
Alex.
Sure.
Vendor branching updating is a bit tricky and requires additional
On 11/21/2013 12:52, Antonio Huete Jimenez wrote:
Hi John,
As I've previously stated, I don't think a roadmap is something
desired,
I think we've seen immediate response from USERS that this is something
desired.
i.e. people should work on whatever areas they want, and not
be forced to
On 11/21/2013 08:23, Daniel Ramos wrote:
As a list lurker keen to contribute to dfly, this road map is definitely
valuable. Thanks for putting it together John.
I'd propose
* update iwn driver to support latest chip sets
As something I'd like to look at (came up on the list the other
On 11/22/2013 03:30, Justin Sherrill wrote:
On Thu, Nov 21, 2013 at 3:19 PM, John Marino dragonfly...@marino.st
mailto:dragonfly...@marino.st wrote:
Right now, maintenance, is about the best we can hope for unless we
either get new blood or vets start producing something substantial
On 11/22/2013 11:41, Alex wrote:
On 11/21/2013 12:31 PM, John Marino wrote:
On 11/21/2013 12:12, Alex wrote:
Thank you for this roadmap. As a newcomer wanting to contribute, it
really helps with an overview of what could be done.
I'll give a try on the bmake update if that's OK :)
Alex
Hi list,
I just wanted to share that we have a volunteer to care after i386
dports (generation and patches) and perhaps even base issues as he
becomes more knowledgeable. His name is Rett Kent, and the introduction
email I received is posted below.
Welcome Rett!
Francois Tigeot (ftigeot) and I
On 11/21/2013 22:40, Francois Tigeot wrote:
On Thu, Nov 21, 2013 at 08:07:25PM +0100, John Marino wrote:
OSS/ALSA - When was the last time somebody in dragonfly touched audio?
Last year.
I just picked a random post to continue.
A couple of our road-map items have already been
On 11/28/2013 12:02, Konrad Neuwirth wrote:
Hello,
I have a rather uncommon request. I'm thinking about making a fairly
small dragonflybsd install image for our production servers. I'm sure
that it doesn't need the compiler tool chain or a lot of other
things; but does anyone here have a
On 11/29/2013 18:48, Cassandra von Ahrcanburg wrote:
Hello everybody!
I've read quite a few of the posts on this list and from what I can
tell there is a certain lack of females. :-) Oh well, with me being a
computer nerd and all I am pretty much used to being around men. :-P
Yeah, if there
On 12/1/2013 17:32, Cassandra von Ahrcanburg wrote:
On Fri, 29 Nov 2013 21:14:58 +0100
John Marino dragonfly...@marino.st wrote:
Graphics board
nVidia is not a good choice for FreeBSD.
AMD Radeons have a slightly more promising future.
I've been told that the nVidia binary driver
On 12/2/2013 15:21, Pierre Abbat wrote:
On Monday, December 02, 2013 07:58:00 Joe Talbott wrote:
If I'm not mistaken that error means there is a problem with your firmware
file. Check that you have the correct version.
How? I know nothing about firmware files.
I'm in the middle of
On 12/2/2013 15:54, Pierre Abbat wrote:
On Monday, December 02, 2013 15:40:40 Joris Giovannangeli wrote:
Not the only one, I've got an issue since I upgraded to 3.7-dev. pkg
search returns nothing. I put 3.8 ABI version in pkg.conf, I check the
mirror, and I've even deleted the db files and
On 12/2/2013 16:24, Pierre Abbat wrote:
On Monday, December 02, 2013 16:13:17 John Marino wrote:
It doesn't matter when you switch kernel or world. You can just upgrade
or wipe out /usr/local + /var/db/pkg and start again followed by pkg clean
The question about when he switched
On 12/4/2013 15:29, Chris Turner wrote:
On 11/27/13 2:06 PM, John Marino wrote:
Mini Roadmap for DragonFly 3.7 Development Branch -
https://docs.google.com/spreadsheet/ccc?key=0AmOIvwOJYx_rdHFpYTFKeEtiRjh0c2xyc0hXQ29Da2cusp=sharing
Isn't this what the wiki is for?
likewise, project git
On 12/4/2013 19:38, Justin Sherrill wrote:
IT MUST COME DOWN NOW FOR VETTING BY THE DRAGONFLY CENTRAL COMMITTEE FOR
TASK APPROVAL.
Kidding, kidding. The process is not as important as the end result,
and it's great that several items on John's list already have been
picked up.
John, if
As yet another example of how our in-between libusb is deeply hurting
us, I'm able to completely build the chromium browser after some heavy
tweaking.
Unfortunately, it doesn't link. It needs the new libusb, and it's
deeply ingrained. I was unsuccessful at removing all functionality that
needs
On 1/5/2014 18:07, John Marino wrote:
As yet another example of how our in-between libusb is deeply hurting
us, I'm able to completely build the chromium browser after some heavy
tweaking.
Unfortunately, it doesn't link. It needs the new libusb, and it's
deeply ingrained. I
On 1/14/2014 04:23, Justin Sherrill wrote:
It's trying to download a prebuilt binary of pkg for i386/DragonFly 3.7.
There isn't one - Marino built packages for 3.6/i386, and has not been
building them for 3.7+. There's a fellow that volunteered to work on
i386 dports, but I don't think he's
On 1/17/2014 18:33, Brad Fitzpatrick wrote:
FYI...
There's currently a discussion on the Go mailing list (golang-dev) about
removing DragonFly BSD support from Go.
Per our porting policy
(https://code.google.com/p/go-wiki/wiki/PortingPolicy) we need a port
maintainer and a continuous
1 - 100 of 273 matches
Mail list logo
