Hi, list! :)
I've finally finished the program and have submitted it to the FreeBSD
ports tree.
Now all is left is to wait till the program gets added to the ports tree.
After it gets added (let's hope so :)) to the FreeBSD ports it will be
under ports-mgmt/pkg_add_it
Meanwhile I've added a
Marin Atanasov wrote:
Thanks, I've read it and now my Makefile is as follows:
PROG= pkg_add_it
SRCS= fnode.c explode.c scan_directory.c scan_index_file.c pkg_add_it.c
.include
.include
It builds, installs, cleans, etc.. but when I `make install' it
finishes successfully, but does not act
Michel Talon wrote:
Marin Atanasov wrote:
Should I add something else to it or modify something?
You should remove a lot, because many implicit rules are already defined
in /usr/share/mk/sys.mk which is sourced by make automatically. See for
example
/usr/src/usr.sbin/pkg_install/add
Marin Atanasov wrote:
> Should I add something else to it or modify something?
You should remove a lot, because many implicit rules are already defined
in /usr/share/mk/sys.mk which is sourced by make automatically. See for
example
/usr/src/usr.sbin/pkg_install/add/Makefile
to discover how litt
This time I need your help to help create my Makefile.
To be honest this will be my first Makefile and I'm not
very sure that it is correctly written although it builds fine.
PROG=pkg_add_it
SRCS=fnode.c explode.c scan_directory.c scan_index_file.c pkg_add_it.c
OBJS=fnode.o explode.o
Hello
On Fri, Oct 03, 2008 at 10:24:37PM +0300, Marin Atanasov wrote:
> I was wondering how to create a man page for my program.
groff_mdoc(7) is probably what you are looking for... Having a look to
existing man pages is also really useful for seeing how things are done.
With kind regards,
Romai
Marin Atanasov <[EMAIL PROTECTED]> writes:
> I was wondering how to create a man page for my program.
> I was looking over the web, and found similar questions already posted,
> but they all suggest that you take an existing copy of a man page and
> edit it for your needs. Isn't there a guide or s
Hi, list - it's me again :)
I was wondering how to create a man page for my program.
I was looking over the web, and found similar questions already posted,
but they all suggest that you take an existing copy of a man page and
edit it for your needs. Isn't there a guide or something on how to
cre
Michel Talon wrote:
Marcin Wisnicki wrote:
Unless I'm missing something there needs to be a MOVED file or ideally
something like it that has pkgnames (with versions) for a binary
package update tool to work.
First, congratulations to Marin Atanasov for having completed his
program! As
Marcin Wisnicki wrote:
> Unless I'm missing something there needs to be a MOVED file or ideally
> something like it that has pkgnames (with versions) for a binary
> package update tool to work.
First, congratulations to Marin Atanasov for having completed his
program! As far as i understand, Mari
On Wed, Oct 1, 2008 at 8:47 PM, Garrett Cooper <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 1, 2008 at 3:18 PM, Marin Atanasov <[EMAIL PROTECTED]> wrote:
>> Alexander Churanov wrote:
>>>
>>> Marin,
>>>
>>> Let me suggest some names:
>>>
>>> 1) pkg_search
>>>
>>> 2) pkg_find
>>>
>>> 3) pkg_install
>>>
>
On Wed, Oct 1, 2008 at 3:18 PM, Marin Atanasov <[EMAIL PROTECTED]> wrote:
> Alexander Churanov wrote:
>>
>> Marin,
>>
>> Let me suggest some names:
>>
>> 1) pkg_search
>>
>> 2) pkg_find
>>
>> 3) pkg_install
>>
>> 4) package-finder
>>
>> 5) package-installer
>>
>> 6) find-package
>>
>> 7) install-pa
Alexander Churanov wrote:
Marin,
Let me suggest some names:
1) pkg_search
2) pkg_find
3) pkg_install
4) package-finder
5) package-installer
6) find-package
7) install-package
8) easy-install
9) interactive-install
Alexander Churanov
Thank you for your support, folks!
By tomorrow th
Marin,
Let me suggest some names:
1) pkg_search
2) pkg_find
3) pkg_install
4) package-finder
5) package-installer
6) find-package
7) install-package
8) easy-install
9) interactive-install
Alexander Churanov
___
freebsd-ports@freebsd.org mailing
Hans F. Nordhaug wrote:
Hm, isn't this a little too generic name? If this is an interactive
version of pkg_add maybe use name that makes that clear?
Hans
Disclaimer: I haven't tried your program/sit.
___
freebsd-ports@freebsd.org mailing list
http://l
* Marin Atanasov <[EMAIL PROTECTED]> [2008-10-01]:
> Hi, again! :)
>
> I've finished the new version of the program. I decided to name it `sit'
> - Simple Interactive Tool
[cut]
Hm, isn't this a little too generic name? If this is an interactive
version of pkg_add maybe use name that makes that
Miroslav Lachman wrote:
It seems useful. I have one suggestion - make it as port and submit PR
for adding it in to ports tree, so it will get wider audience :)
Miroslav Lachman
Will do that :) Maybe tomorrow I'll start making the port, because right
now I have to study for my exams.
It seem
Marin Atanasov wrote:
Hi, again! :)
I've finished the new version of the program. I decided to name it `sit'
- Simple Interactive Tool
`sit' now supports the following:
-- improved code for dynamic memory allocation
-- local package pattern search
-- remote (ftp) package pattern search
-- c
Hi, again! :)
I've finished the new version of the program. I decided to name it `sit'
- Simple Interactive Tool
`sit' now supports the following:
-- improved code for dynamic memory allocation
-- local package pattern search
-- remote (ftp) package pattern search
-- command line arguments to
On Mon, Sep 29, 2008 at 04:08, Garrett Cooper <[EMAIL PROTECTED]> wrote:
> On Sun, Sep 28, 2008 at 2:28 PM, Marcin Wisnicki <[EMAIL PROTECTED]> wrote:
>> Would be nice if there was also INDEX.bz2.
>
> You'd need to talk to the release team about that if you don't agree
Indeed
> with that fact; IND
Garrett Cooper wrote:
Try fetch(3).
You can get all of this information, again, from INDEX with or without pkg_info.
-Garrett
Yes, I'll use fetch(3) - that's what I meant, probably I didn't explain
it well that's why you've misunderstood me :)
Currently I'm writing the functions which w
On Mon, Sep 29, 2008 at 4:39 AM, Marin Atanasov <[EMAIL PROTECTED]> wrote:
> Michel Talon wrote:
>
>> I can only concur with the suggestion you mention, exploring ftp sites
>> to discover what is available here. How to do that efficiently is
>> harder. Apparently "official" FreeBSD ftp sites have a
Michel Talon wrote:
> I can only concur with the suggestion you mention, exploring ftp sites
> to discover what is available here. How to do that efficiently is
> harder. Apparently "official" FreeBSD ftp sites have an INDEX of
> available packages. I hope it is reliable. Then i suggest to downlo
On Sun, Sep 28, 2008 at 2:28 PM, Marcin Wisnicki
<[EMAIL PROTECTED]> wrote:
> On Sat, 27 Sep 2008 21:11:27 -0700, Garrett Cooper wrote:
>
>> On Sat, Sep 27, 2008 at 7:02 AM, Michel Talon <[EMAIL PROTECTED]>
>> wrote:
>>> Marin Atanasov wrote:
>>>
So what do you think - is it worth improving up
On Sat, 27 Sep 2008 21:11:27 -0700, Garrett Cooper wrote:
> On Sat, Sep 27, 2008 at 7:02 AM, Michel Talon <[EMAIL PROTECTED]>
> wrote:
>> Marin Atanasov wrote:
>>
>>> So what do you think - is it worth improving upon it or it's a waste
>>> of time?
>>> Thanks for any suggestions.
>
> INDEX is mad
On Sat, Sep 27, 2008 at 7:02 AM, Michel Talon <[EMAIL PROTECTED]> wrote:
> Marin Atanasov wrote:
>
>> So what do you think - is it worth improving upon it or it's a waste of
>> time?
>> Thanks for any suggestions.
>
> I think it is worth improving and certainly not a waste of time.
> Each work whic
Marin Atanasov wrote:
> So what do you think - is it worth improving upon it or it's a waste of
> time?
> Thanks for any suggestions.
I think it is worth improving and certainly not a waste of time.
Each work which allows to use precompiled packages more efficiently
in FreeBSD is very useful, in
Hello everyone! :)
I have a program I wrote 1 or 2 days ago for a friend who was asking about
how to make pkg_add install a package from a specific local path and if
the package is not there then pkg_add should install it remotely (using
the -r option). Of course this is not a new pkg_add version
28 matches
Mail list logo
