=== macd_ is now known as macd [02:32] hmm. it's never good when the first page of google search for an idea contains a patent hit [02:34] A software patent? Just ignore it. :-P [02:35] i wasn't planning on implementing it anyways [02:35] i could see a future where software patents exist [02:36] 3 year terms and working source code [02:42] fortunately, it looks like they're all taking my small idea and building something bigger with it, rather than claiming the small idea as their own [02:42] just lookin to see if there's a standard way of doing DAGs in XML [08:02] Keybuk: ping? [09:03] G'morning [12:22] Hi [12:22] Does anyone know how to properly package a autotools build app? [12:29] LCID_Fire: Almost everyone here, I'd wager. [12:31] LCID_Fire: In fact, it's the default, for any packaging guide you might find. [12:32] the guides I found till now are not very clear about this :( [12:33] LCID_Fire: Which guide? [12:33] HI All how to sync wm6 smatphone in linux ? [12:33] brt: The first step is to read the topic. [12:34] brt: You'll want to ask that question on #ubuntu, or if there is no response, post it on questions.launchpad.net/ubuntu [12:35] ah thx [12:36] LCID_Fire: Oh, is this writing the autofoo to _build_ said app, or doing the Debian packaging? [12:37] RAOF: Autotools chain is running fine - but packaging the whole thing for debian is confusing me pretty much === Kopfgeldjaeger2 is now known as Kopfgeldjaeger [12:39] LCID_Fire: In short, just make sure that debian/rules build contains everything required to build the package, including any autotools stuff. [12:39] I have - but now it complains about the autocreated files [12:40] When does it complain? [12:40] e.g.: [12:40] dpkg-source: cannot represent change to INSTALL: [12:40] dpkg-source: new version is plain file [12:40] dpkg-source: old version is something else [12:41] You also need to make sure debian/rules clean restores the directory to the state it had prior to debian/rules $(anything else) [12:42] That would mean I'd have to remove all autocreated files!? [12:42] Yes. [12:43] I just hope there is some call to do this easily [12:59] Did not really help. I now added ./autogen.sh and ./configure before doing 'make distclean' but it still complains [12:59] Is there not already a nice clean upstream tarball? (Presumably not) [13:00] It’s better to run the auto* stuff yourself and let it stay in the diff. [13:00] No it's my own app ;) [13:00] LCID_Fire: Then why don't you release a tarball with "make dist"? [13:00] Nice and easy. [13:01] Because I don't know shit about debian packaging!? [13:01] That’s not related to Debian at all. [13:03] Where is the difference between make dist and make install? [13:03] one makes a dist tarball of the source, the other installs the compiled program to your system [13:05] k, but I still need to compile & package the tarball since I have users that are presumably not experienced enough to compile for themselfs [13:07] LCID_Fire: Sure, but you'll find it easiest if you get the upstream tarball all perfect first, and then package it. Less confusing that way. [13:07] Traditionally, the way to distribute a release is with a tarball made by make dist (note: for added bonus marks, ensure that make distcheck works) [13:08] That way, people don't need to mess with the autofoo; they just run ./configure [13:09] Does anyone have a good tutorial on make dist? Google is not very good for such topics [13:09] Its an automagic target created by autotools. [13:10] It basically tar-s up everything that's needed to build the package. [13:13] Ok, I fixed it. I had an error in a configuration switch I usually never compile - which 'make dist' chocked on [13:13] morning [13:13] more like good afternoon :) [13:17] Depends on one's location. It's even night some places :p [13:17] Not to mention one's getting up habits :) [13:24] k, I give up - not in the mood fore more headache anymore. Thanks for now though === |Baby| is now known as Baby === bliZZardz is now known as bliZZardz_ === bliZZardz_ is now known as bliZZardz [15:35] nixternal: ping [15:39] brandonperry_: pong? [15:39] uh, I had a question about install KDE4.1-beta 2 for leonov, but I was tol dto go to #leonov [15:40] but thanks for responding :-) [15:40] np [19:22] pitti, doko: Any chance one of you is around? [19:25] cjwatson: ? [19:52] hello [19:52] I need some help to create a paquet debian for ubuntu [19:53] need to transfert ini files into $home dir of user [19:53] in the structure /etc/skel do this ? [19:57] eric_medintux: there's better channels than this for packaging questions [19:58] eric_medintux: 1) #ubuntu-motu 2) what you're trying to do is against debian policy [19:58] BenC : which ones ? [19:58] eric_medintux: #ubuntu-motu [19:59] Chipzz : ok thanks. against debian policy ? Lots of apps put things into $home/.*** [19:59] this is not recommanded ? [19:59] eric_medintux: they create them in $HOME when the app is run, not when it is installed [19:59] eric_medintux: You cannot install config files in every $HOME when the package is installed :) [20:00] eric_medintux: let me clarify: you are allowed to put files in /etc/skel . You are (for obvious reasons) NOT allowed to touch any file in users homedirs [20:00] BenC : Ok my app need to install not the package [20:00] eric_medintux: ok, then that's not a packaging question at all [20:00] eric_medintux: and /etc/skel is the wrong place [20:01] what is the right place ? [20:01] eric_medintux: if your app needs to copy it from somewhere when it is started up, then the best place is /usr/share//base.config or something [20:01] eric_medintux: the reason is very simple: by creating or changing files in the users homedir, you are altering the behaviour of applications, which the user didn't ask for [20:01] ok but this is a supplementary step into getting app working [20:01] Chipzz: your confusing this, applications are allowed to modify their own config files in a users homedir [20:01] anyway -> #ubuntu-motu [20:02] Chipzz: that has nothing to do with packaging [20:02] my files does contain only user parameters [20:02] BenC: no I'm not confused. just trying to explain him why packages can't alter files in the users' homedir [20:02] Chipzz: he's not asking for the package to change it, his app is === fta_ is now known as fta [20:04] Benc, Chippzz : I'm french so... I wish my package to install *.ini of my app into $home. Maybe creating a group named ? [20:04] then user tells i want to be a myapp user and get the ini files [20:04] eric_medintux: Uh, now you're way off base...go to #ubuntu-motu [20:04] K bye and thank you for all. [23:11] any people on to help me with something real quick on a definition [23:14] !ask [23:14] Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-) [23:15] what is this error mean "svn: Malformed network data" [23:16] Yud_Zroc: You want to ask in a Subversion channel, I believe. [23:16] As it's not Ubuntu development, and it's not really Ubuntu at all. [23:16] ok tyvm for the tip [23:17] do u know what the channel is called