Armin K. wrote:
> Are you sure that you have used the correct patch?
That's it. I had the -1 patch, not the -2 patch in my files and didn't
notice the change. Thanks. That's why I was confirming.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfrom
On 12/14/2012 06:09 PM, Bruce Dubbs wrote:
>
> I got some of those warnings, but got errors. too:
>
> /tmp/k3b/k3b-2.0.2/plugins/decoder/ffmpeg/k3bffmpegwrapper.cpp:91:15:
> error: '::av_open_input_file' has not been declared
>
> /tmp/k3b/k3b-2.0.2/plugins/decoder/ff
Armin K. wrote:
> On 12/14/2012 05:25 AM, Bruce Dubbs wrote:
>> I was trying to build k3b today and ran into some problems with ffmpeg.
>> I did apply the existing patch, but that wasn't enough.
>>
>> Searching the web, I found
>>
>> http://lists
On 12/14/2012 05:25 AM, Bruce Dubbs wrote:
> I was trying to build k3b today and ran into some problems with ffmpeg.
>I did apply the existing patch, but that wasn't enough.
>
> Searching the web, I found
>
> http://lists.opensuse.org/opensuse-kde3/2012-07/msg0001
I was trying to build k3b today and ran into some problems with ffmpeg.
I did apply the existing patch, but that wasn't enough.
Searching the web, I found
http://lists.opensuse.org/opensuse-kde3/2012-07/msg00019.html
Applying the equivalent of this patch allowed the program to build an
as symlinks of not.
>>
>> -- Bruce
>
> cdrkit is actually a fork of cdrtools [1]. These symlinks can be made
> for the compatibility with cdrtools:
>
> ln -s wodim /usr/bin/cdrecord
> ln -s readom /usr/bin/readcd
> ln -s genisoimage /usr/bin/mkisofs
> ln -s
mlinks can be made
for the compatibility with cdrtools:
ln -s wodim /usr/bin/cdrecord
ln -s readom /usr/bin/readcd
ln -s genisoimage /usr/bin/mkisofs
ln -s genisoimage /usr/bin/mkhybrid
ln -s icedax /usr/bin/cdda2wav
Brasero can use wodim by default, without any need for cdrkit
compatibility. Also
Armin K. wrote:
> I still think we should use cdrkit instead of that one.
I got that and it built fairly easily but some binaries are different:
cdda2mp3 devdump genisoimage isodebug isoinfo pitchplay readom
cdda2ogg dirsplit icedax isodump isovfy readmult wodim
cdrtools ha
On Fri, May 04, 2012 at 05:14:53AM -0600, Matthew Burgess wrote:
> On Fri, 4 May 2012 12:05:45 +0100, Andrew Benton wrote:
>
> > I think we removed it because we don't like Jörg Schilling
>
> I think it's more the case that Jorg Schilling doesn't like us (Linux) :-)
>
For those of us who have
On Fri, 4 May 2012 12:05:45 +0100, Andrew Benton wrote:
> I think we removed it because we don't like Jörg Schilling
I think it's more the case that Jorg Schilling doesn't like us (Linux) :-)
I don't see any good reason to have software in the book that is going to
bitch and moan so loudly and
On Fri, 04 May 2012 00:34:09 +0100
Bruce Dubbs wrote:
> Whew. I finally got k3b to build and work properly. There are a lot of
> dependencies that I didn't know about and there are run time dependencies too.
>
> One runtime dependency is cdrecord (cdrtools). I don't
On 05/04/2012 01:32 AM, Bruce Dubbs wrote:
> Whew. I finally got k3b to build and work properly. There are a lot of
> dependencies that I didn't know about and there are run time dependencies too.
>
> One runtime dependency is cdrecord (cdrtools). I don't recall wh
Whew. I finally got k3b to build and work properly. There are a lot of
dependencies that I didn't know about and there are run time dependencies too.
One runtime dependency is cdrecord (cdrtools). I don't recall why we removed
it, but cdrtools-3.00.tar.bz2 from June 2010 seems to
> > Could you please verify that it doesn't introduce bugs similar to
> > http://wiki.linuxfromscratch.org/blfs/ticket/2227 ? I.e., KDE
> > programs should be visible in menus of other desktops, possibly
> > including Xfce (currently commented out due to bugs and the fact
> > that I no longer use i
> > --sysconfdir=/etc/kde
>
> Could you please verify that it doesn't introduce bugs similar to
> http://wiki.linuxfromscratch.org/blfs/ticket/2227 ? I.e., KDE
> programs should be visible in menus of other desktops, possibly
> including Xfce (currently commented out due to bugs and the fact that
>
Alexander E. Patrakov wrote:
> Bruce Dubbs wrote:
>
>> --sysconfdir=/etc/kde
>
> Could you please verify that it doesn't introduce bugs similar to
> http://wiki.linuxfromscratch.org/blfs/ticket/2227 ? I.e., KDE programs should
> be
> visible in menus of other desktops, possibly including Xfce
Bruce Dubbs wrote:
> --sysconfdir=/etc/kde
Could you please verify that it doesn't introduce bugs similar to
http://wiki.linuxfromscratch.org/blfs/ticket/2227 ? I.e., KDE programs should
be
visible in menus of other desktops, possibly including Xfce (currently
commented
out due to bugs and t
Randy McMurchy wrote:
> Bruce Dubbs wrote these words on 03/10/08 22:23 CST:
>
>> That's a personal preference. I can live with the book either way, but
>> I prefer /opt/kde. I believe, but haven't checked for sure, that
>> existing config files are not overwritten by an install.
>>
>> Or, I sup
Bruce Dubbs wrote these words on 03/10/08 22:23 CST:
> That's a personal preference. I can live with the book either way, but
> I prefer /opt/kde. I believe, but haven't checked for sure, that
> existing config files are not overwritten by an install.
>
> Or, I suppose, create a symlink.
I cut
Randy McMurchy wrote:
> I'm one that thinks the KDE instructions should individualize the
> /etc/ dirs to a version-specific directory.
>
> I think that every installation should have an independent file
> structure. GNOME is that way now. Currently KDE uses /etc/kde which
> would be overwritten/
Robert Daniels wrote these words on 03/10/08 21:37 CST:
> On Sunday 09 March 2008 05:44:32 Robert Daniels wrote:
>> If there are no objections by then, I will go
>> ahead and remove the notes.
>>
> Notes have been commented out in the xml. If someone objects, I can add
> them back or possibly mo
On Sunday 09 March 2008 05:44:32 Robert Daniels wrote:
> If there are no objections by then, I will go
> ahead and remove the notes.
>
Notes have been commented out in the xml. If someone objects, I can add
them back or possibly move to pre-install page, with slight wording
changes.
--
Robert
On Saturday 08 March 2008 15:31:31 DJ Lucas wrote:
> Just in case it got lost in the KDE thread, I thought I'd bring it up
> again. The note about the kde-sysconfdir on the three pages in the
> subject seems like a bit too much hand holding to me, and IMO should
> be removed. Either you follow th
Just in case it got lost in the KDE thread, I thought I'd bring it up
again. The note about the kde-sysconfdir on the three pages in the
subject seems like a bit too much hand holding to me, and IMO should be
removed. Either you follow the books instructions or you get to keep
all the pieces
Attached is a patch to upgrade k3b to 1.0.4
This turned out to be a simple version bump. All the explanatory text
appears to still apply.
The dependencies listed on the K3b requirements page are the same as
listed in the book. The changelogs say that libcdio can now optionally
be used
Thanks to all those who contributed to my questions about the KDE
and K3b installation. To Bruce: I didn't think we would do a special
change in the KDE instructions to modify the installation, I figured
you would just do the change at the next version update. My reason
for asking is t
apps go in $KDE_PREFIX, I would say. The issue is with
>> type 2 apps, and I guess I'd go for $KDE_PREFIX.
>
> Good observation, Richard. Now to figure out where K3b stands. :-)
>
> I believe it to be a cross between 2 and 3, perhaps leaning to 3 more
> than 2. Here is
On 3/15/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> I'm not trying to argue with you, Dan, I'm only pointing out these items
> as I'm looking for a community decision on where we should install K3b,
> and I'm thinking these data facts may help with th
Dan Nicholson wrote these words on 03/15/06 12:30 CST:
>>I haven't tested much, but I agree with Richard that this is an app
>>that only uses kdelibs.
>
> Sorry for contradicting myself in the message. I should say that K3b
> can be built with only kdelibs. Later in
On 3/15/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
>
> I haven't tested much, but I agree with Richard that this is an app
> that only uses kdelibs.
Sorry for contradicting myself in the message. I should say that K3b
can be built with only kdelibs. Later in the messag
On 3/15/06, Richard A Downing <[EMAIL PROTECTED]> wrote:
> >
> > Where should K3b be installed, /usr or $KDE_PREFIX?
>
> There appear to be at least three kinds of so called KDE applications:
>
> 2) Those that use KDE libs, but don't depend on the whole of KD
apps, and I guess I'd go for $KDE_PREFIX.
Good observation, Richard. Now to figure out where K3b stands. :-)
I believe it to be a cross between 2 and 3, perhaps leaning to 3 more
than 2. Here is some additional info that may make it easier to make a
decision where to install it.
1. I
Randy McMurchy wrote:
> And we're already probably *way* off-topic
> for BLFS-Dev. (hmm, should RMLCopyDVD be a BLFS package?) :-)
The standard way is to write a hint or put it in the wiki. :)
> To others who feel this is off-topic for BLFS-dev, I send my
> sincere apologies and ask for your su
Dan Nicholson wrote:
On 3/5/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
I created a tarball of this script and support programs, some docs
and man pages and learned the GNU Autotools (very, very cool once
you learn autoconf and automake language) to package them. More than
anything this turne
On Sun, 2006-03-05 at 17:03 -0800, Dan Nicholson wrote:
> On 3/5/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> >
> > I created a tarball of this script and support programs,
>
> This looks really good, Randy.
Dan, I cannot tell you how grateful I am that you downloaded and
looked at this. Kind
On 3/5/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> I created a tarball of this script and support programs, some docs
> and man pages and learned the GNU Autotools (very, very cool once
> you learn autoconf and automake language) to package them. More than
> anything this turned into an exerc
[CC'd to BLFS-Dev as an update on the K3b addition]
Hi all,
I queried the groups not too long ago about what folks used as a GUI
interface (primarily in KDE) to to a DVD/CD copy program. K3b was
resoundingly recommended. Indeed, it is a very nice program, and
deserves a place in
Randy McMurchy wrote:
We agree on this point. I believe DJ offered an opinion on this
as well that dvd+_rw-tools should be in the book.
Sorry I didn't offer an opinion. Thanks for adding it to the book.
Andy
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscra
Randy McMurchy wrote:
> I propose that we change the name of the chapter to "Chapter 41 -
> CD/DVD Writing Utilities".
>
> Any objections?
No.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above info
Dan Nicholson wrote these words on 02/09/06 16:58 CST:
> Randy, these instructions work for me.
>
> make
> make rpl8 btcflash
> make prefix=/usr install
> mkdir -pv /usr/share/doc/dvd+rw-tools-6.1
> install -v -m 644 index.html \
> /usr/share/doc/dvd+rw-tools-6.1
Looks good to me, Dan. Mucho
On 2/9/06, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> I also found that 'make install' produces errors (though insignificant
> at the end of the installation) which can lead to confusion if this
> package is put in the book.So, here are our choices.
> 1. Not put dvd_rw-tools in BLFS.
No, I t
Hi all,
Turning away from GNOME for awhile, I started playing with the K3B
CD/DVD program. All who recommended it know what they're talking about.
It is very good software.
Definitely should be in the book. Too bad about the monster dependency
list, though. One of the dependencies (listed o
Randy McMurchy wrote:
> You can check out the home page at: http://www.k3b.org/
>
> It appears it requires KDE, (and of course Qt) and the aforementioned
> packages, along with many other optional dependencies.
Looks good. It would be a good addition to BLFS.
-- Bruce
--
http://linuxfromsc
Bruce Dubbs wrote these words on 05/26/05 23:23 CST:
> I'm not familiar with either package. K3B, from your description above,
> is an alternative to cdrecord. resman displays writing status? From
> your description, they are both KDE apps, correct?
>
> Can you point to
Bruce Dubbs wrote:
DJ Lucas wrote:
Hi guys. I found a new burning program and absolutely love it - K3B.
Well new to me being it's a KDE app, but it looks equally good
(respecting your gtk2 theme) in gnome. Reminds me much of Nero-5 on
Windows. In order to make it display writin
DJ Lucas wrote:
> Hi guys. I found a new burning program and absolutely love it - K3B.
> Well new to me being it's a KDE app, but it looks equally good
> (respecting your gtk2 theme) in gnome. Reminds me much of Nero-5 on
> Windows. In order to make it display writing and
Hi guys. I found a new burning program and absolutely love it - K3B.
Well new to me being it's a KDE app, but it looks equally good
(respecting your gtk2 theme) in gnome. Reminds me much of Nero-5 on
Windows. In order to make it display writing and buffer status, it
needs resource manager.
47 matches
Mail list logo
